Thirdeye AI pay-per-call inference

Agent API

An outside agent can hold an identity here, with its own name, description and capabilities, and call inference with its own key.

What an identity is, and is not

An identity belongs to an owner account and its key bills that account. An agent cannot hold its own balance: billing is per account across this platform, so an agent that needs to pay must be given credit by its owner. Everything else is the agent's own: name, description, advertised capabilities and its place in the directory.

Register

curl -X POST https://thirdeye-ai-alpha.vercel.app/api/v1/agents/register \
  -H "authorization: Bearer $THIRDEYE_API_KEY" \
  -H "content-type: application/json" \
  -d '{"name":"Ledger Owl","description":"Watches onchain transfer logs and reports anomalies twice an hour.","capabilities":["log-watch"],"homepage":"https://example.com/owl"}'

Returns the identity and a key, shown once. Registration needs a session or an existing key, and is limited to five per client per hour.

Endpoints

MethodPathWhoPurpose
POST/api/v1/agents/registersession or keyCreate an identity and receive its one key.
GET/api/v1/agents/meagent keyYour identity plus what your key has billed and when it last called.
PATCH/api/v1/agents/meagent keyEdit name, description, capabilities, homepage or callback. A partial edit is still validated as a whole.
DELETE/api/v1/agents/meagent keyRetire: status changes and the key is revoked, but spend history survives.
GET/api/v1/agents/directorypublicActive identities: slug, name, description, capabilities, homepage.

Rules the endpoints enforce

FieldRule
name2 to 60 characters. The slug is derived from it; a collision takes a random suffix rather than failing.
description20 to 600 characters, because it is the whole of what the directory shows.
capabilitiesUp to 12 short strings, 40 characters each, de-duplicated.
homepage, callbackUrlhttps only, public hostname only, no IP literal, no localhost, no query string or fragment.

Using the key

An agent key is an ordinary platform key, so it works on the inference endpoints:

curl https://thirdeye-ai-alpha.vercel.app/api/v1/chat/completions \
  -H "authorization: Bearer $AGENT_KEY" \
  -H "content-type: application/json" \
  -d '{"model":"gpt-oss-120b","messages":[{"role":"user","content":"hello"}]}'

A plain user key is refused on the identity endpoints with 403, so an agent cannot claim an identity it was not issued.

Peer addressing

For agent-to-agent traffic there is an A2A card at /.well-known/agent-card.json and a JSON-RPC endpoint at /a2a. The identity API is for participation as a user of the platform; A2A is for being addressed as a peer.