Your AI Agent Needs an Account
ATXP gives AI agents identity, payments, email, and 14+ tools in one account. One command. No API key management. Pay only for what your agent uses.
npx atxp Creates a complete agent account in seconds The Problem You're Probably Hitting
Every new AI model ships with the same problem: another account, another API key, another subscription. Your billing is scattered across Anthropic, OpenAI, Stability, a search API, a storage service, and a half-dozen other providers. Each key needs to be rotated, each subscription needs to be renewed, and none of them know about each other.
When something breaks, the debugging path starts with "which of the seven API keys is invalid?" When your agent needs a capability you haven't pre-wired, you stop to sign up for a new service. When you want to switch from Claude to GPT-4 (or back), you re-engineer the client code.
This is not an agent problem. It is an infrastructure problem.
What ATXP Does Instead
ATXP is a single account for your AI agent — bundling everything an agent needs to operate autonomously.
| Without ATXP | With ATXP |
|---|---|
| API key per model provider | One account, all models via LLM gateway |
| Separate billing per service | Single IOU token balance, one billing source |
| Agent has no persistent identity | Agent handle persists across sessions |
| No payment method for the agent itself | Agent pays for tool calls autonomously |
| New model → re-engineer the API client | New models appear automatically via gateway |
| Agent can't receive messages or emails | @atxp.email address, instantly usable |
What Your Agent Gets
How to Get Started
npx atxp Creates a complete agent account: handle, 10 starter IOU tokens, @atxp.email address, and tool access. No email verification. No credit card form.
npm install @atxp/sdk The SDK provides convenience wrappers for all ATXP tools. The underlying API is REST — you can call it from any language or framework without the SDK.
// LLM inference via the gateway
const response = await atxp.llm.complete({
model: 'claude-3-7-sonnet-latest',
messages: [{ role: 'user', content: prompt }]
});
// Image generation
const image = await atxp.image.generate({
prompt: 'A diagram showing agent architecture'
});
// Web search
const results = await atxp.search.query({
q: 'ATXP agent transaction protocol'
}); Each tool call deducts IOU tokens at at-cost passthrough rates. Purchase additional tokens when the balance runs low. No subscriptions, no minimums.
Pricing: What You Actually Pay
ATXP is pay-as-you-go. Account creation is free. You pay only for what your agent uses.
| Item | Cost |
|---|---|
| Account creation | Free |
| Starter IOU tokens | 10 tokens, free on registration |
| Additional tokens | Purchased as needed, at-cost passthrough |
| Monthly fee | None |
| Minimum commitment | None |
Frequently Asked Questions
What is ATXP for developers?
ATXP is infrastructure that gives AI agents an account: a persistent identity, payment capability, email address, and access to 14+ tools from one command. It replaces the need to manage separate API keys, subscriptions, and billing for each AI service your agent uses.
What API keys does ATXP replace?
ATXP replaces the need to individually manage API keys for Anthropic (Claude), OpenAI (GPT-4), Google (Gemini), image generation services, web search APIs, file storage services, video generation APIs, and music generation services. Your agent calls ATXP; ATXP routes to the right provider.
What agent frameworks does ATXP support?
ATXP is framework-agnostic. It works with LangChain, CrewAI, Claude Code, the OpenAI Agents SDK, AutoGen, and any framework that can make HTTP calls. The ATXP SDK provides convenience wrappers; the underlying protocol is REST.
Can multiple agents share one account?
Yes, but each agent should have its own account. Multiple agents sharing one account lose individual identity — you can't tell which agent made which call. ATXP accounts are free to create, so giving each agent its own account is the recommended pattern for auditability and control.
What happens when an agent's token balance hits zero?
Tool calls return an insufficient balance error. The agent cannot make further tool calls until the account is topped up. The agent handle, identity, and account remain intact — only tool access is paused. Top up and the agent resumes immediately.
Give your agent an account.
Get started —npx atxp