Run an unattended agent job with its own key

An unattended agent job is a cron job, timer or CI runner you host that signs in to CoreSpeed as an agent of its own. Its sk-csa- key carries a monthly spend cap, reaches only what is shared with it, and sends a held write to the agent's owner. Every call lands in Activity under the agent's name.

The job. Give a cron job or CI runner you host its own agent identity, a capped key and an owner who answers for it.

Paste this into Claude Code, Codex or Cursor

set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl), then create an agent called nightly-report, mint it an agent key with a 5,000-credit monthly cap, and show me the MCP config my cron job should use, with the key read from CORESPEED_API_KEY.

One prompt.Three steps.

Set up first. Share the accounts the job uses, such as GitHub or Notion, with the organization or with the agent; it reaches Slack and Linear through the app an admin installs. An agent key never reaches a member's other private connections.

  1. Create the agent and its key

    Paste the prompt into Claude Code, Codex or Cursor, signed in as you. You become the agent's owner.

  2. Hand the key to your scheduler

    Keep the key in your secret store and read it from CORESPEED_API_KEY. Cron, a systemd timer or a CI runner starts the job.

  3. Read what it did

    Every call lands in Dashboard → Activity under the agent. A write your policy holds waits for you, its owner.

The full write-up, on the blog →

The tools it calls

  • manage__agents_create · Create the agent; you become its owner
  • manage__agents_key_create · Mint its sk-csa- key with a monthly cap
  • manage__whoami · Check the job signs in as the agent
  • manage__approval_wait · At run time, wait on a held write
Illustrative example · Fictional data

Everything your agents need, one line away.

Give this to your agent

set up https://corespeed.io/SKILL.md
Get started
FAQ

Questions people ask.