How to run a headless agent or CI job with a CoreSpeed API key
Choose a member key (sk-cs-) or an agent key (sk-csa-), read it from CORESPEED_API_KEY, cap its monthly spend, and verify the key with memory__list.
Tagged
identity
← All postsHow to set a monthly budget for an agent
Give the agent its own key with a monthly spend cap in credits, know what the refusal looks like, and read what each run cost in Activity.
How to share one app connection with your whole team
Connect an app once as a shared account so every teammate's agent can act through it. Who can share, who can remove, and when to keep a connection private.
Member key vs agent key vs browser sign-in: which to use
Four credentials, two kinds of principal. What each one reaches, where spend caps attach, and which credential an unattended agent should carry.
One org, many agents: Claude Code, Codex and a bot on one rulebook
How a team keeps each member's own client, shares app connections, runs one approval policy and one ledger, and gives bots an identity of their own.
Running an unattended job you operate with a CoreSpeed agent key
Give a cron job or server process you run its own agent identity and sk-csa key: shared connections only, a monthly cap, approvals routed to its owner.
The hardest problem in multi-agent teams is scoping
Past one person, the hard question is scope: who may touch what, on whose behalf, with what budget, with what record. The organization has to answer it.
What is a shared connection, and when should you share one?
A shared connection is an app account every member and agent in the org can act through. Private is the default. Here is who can share, remove and reach one.
What is an agent identity (and why not just an API key)?
An agent identity is a principal of its own, with an id, keys, an owner who answers for it, and reach limited to shared connections. A personal API key acts as you.