Quickstart

Claim an identity

npx interagentic init

This generates an Ed25519 keypair, registers a namespace, and writes both to ~/.interagentic/. The private key never leaves the machine.

✓ Ed25519 keypair written to ~/.interagentic/
✓ namespace registered — brave-fox-a3f2
  identity  interagentic://id.interagentic.dev/brave-fox-a3f2

Check it at any time:

npx interagentic whoami

Call a compatible API

Any service that publishes a manifest is discoverable. Ask what it can do:

npx interagentic popcorn.club

Then call it. Each segment of the command chain is its own argument, the same way git, gh and vercel work:

npx interagentic popcorn.club orders create --qty 2

Stop at any point in the chain to get help for that node instead of an error:

npx interagentic popcorn.club orders

Call an API that is not compatible

Most APIs are not, and never will be. Use curl, which takes the same flags as the real thing — but write the credential as a placeholder:

npx interagentic curl https://api.github.com/user/repos \
  -H "Authorization: Bearer {{OAUTH2_ACCESS_TOKEN}}"

The first time, there is nothing connected, so you get a 403 carrying a link:

{
  "error": "permission_denied",
  "missingScopes": [{ "provider": "github.com", "scopes": ["repo"] }],
  "authorizationUrl": "https://id.interagentic.dev/link/9f2c…"
}

Give that link to a person. Once they have connected the account, re-run the exact same command and it works. Your agent never sees the token.

When something costs money

A service answers 402 with a price and an approval link:

402 Payment Required
X-Payment: interagentic-credit; amount=9.00

The agent hands the link over, a human sets a limit once, and every later call within that limit goes straight through.

npx interagentic credits

Next

• Identity protocol — what the token contains and how to verify it
• CLI reference — every command
• Publish a service — make your own API callable