Five focused APIs for AI agents. Memory, tools, verification, economy, and reasoning provenance. One API key, simple REST endpoints, production-ready.
Three steps to your first API call. Under 60 seconds.
curl -X POST https://api.agenttool.dev/v1/memories \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "semantic",
"content": "User prefers concise replies. Timezone: UTC+8.",
"key": "user-prefs",
"agent_id": "agent-42"
}'
{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"created_at": "2026-03-09T12:00:00Z"
}
curl -X POST https://api.agenttool.dev/v1/memories/search \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "how does the user like to communicate?"}'
import { AgentTool } from '@agenttool/sdk' const at = new AgentTool() // reads AT_API_KEY from env // Store await at.memory.store("User prefers concise replies", { key: "user-prefs" }) // Search const results = await at.memory.search("communication style", { limit: 3 })
Five services. Each does one thing well. All composed under a single API key.
Store, retrieve, and semantically search agent memories across sessions. Namespaced by key and agent.
BetaWeb search, page scraping, browser automation, and code execution. The agent's hands.
LiveAI-powered fact-checking. Submit a claim, get a verdict with evidence and confidence score.
LiveWallets, micro-billing, escrow, and agent-to-agent value exchange. The economic layer.
LiveReasoning provenance for AI agents. Store and search the WHY behind agent decisions โ not just what happened, but how it was reasoned.
All API requests require a Bearer token in the Authorization header.
Authorization: Bearer YOUR_API_KEY
Base URL: https://api.agenttool.dev โ all endpoints are relative to this.
Projects are the top-level resource. Each project has a credit balance, a plan, and one or more API keys.
Create a new project and receive your first API key. The key is shown once โ store it immediately.
curl -X POST https://api.agenttool.dev/v1/projects \
-H "Content-Type: application/json" \
-d '{"name": "my-agent"}'
{
"project_id": "54b26f66-10ff-466e-a1ab-c793c4d65958",
"name": "my-agent",
"plan": "dev",
"credits": 100,
"api_key": "at_abc123..."
}List all active (non-revoked) API keys for your project. Full key values are never returned โ only prefix and metadata.
curl https://api.agenttool.dev/v1/keys \ -H "Authorization: Bearer YOUR_API_KEY"
Create an additional API key for your project. The api_key is shown once โ store it immediately.
curl -X POST https://api.agenttool.dev/v1/keys \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "production"}'
Revoke an API key by ID. The key ID is returned from GET /v1/keys. Revocation is permanent โ the key cannot be re-activated.
curl -X DELETE https://api.agenttool.dev/v1/keys/KEY_ID \ -H "Authorization: Bearer YOUR_API_KEY"
All errors return JSON with a detail field. Common status codes:
| Status | Meaning | What to do |
|---|---|---|
| 401 | Unauthorized | Check your API key. Make sure it's in the Authorization: Bearer header. |
| 404 | Not Found | Resource doesn't exist. Double-check the ID or key. |
| 422 | Validation Error | Request body is malformed. Check required fields and types in the docs. |
| 429 | Rate Limited | Too many requests. Back off and retry with exponential delay. |
| 500 | Internal Error | Our fault. Retry once, then contact support if it persists. |
{
"detail": [
{
"loc": ["body", "content"],
"msg": "field required",
"type": "missing"
}
]
}
| Plan | Requests / month | Memory retention |
|---|---|---|
| Hatchling (Free) | 10,000 | 30 days |
| Builder ($29/mo) | 500,000 | 1 year |
| Scale ($99/mo) | 5,000,000 | Unlimited |