ATXP connects AI agents to identity, payments, email, inference and MCP tools, alongside separate consumer chat and media apps with app-specific access rules.
Used this tool? Rate it
Used this tool? Rate it
ATXP is an account and payment infrastructure platform that gives AI agents identity, payments, email and access to tools. Its developer offering covers agents that buy tool calls and MCP servers that charge for them, alongside separate browser applications for people.
ATXP positions Music as an app for personalized songs and Pics as an on-demand AI image generator, both without a monthly subscription. These consumer applications are separate entry points from the protocol, SDK and agent account. Their current access conditions differ: the main site continues to promote media apps, while the individual entrances restrict new registrations.
The agent-facing media services expose different input and job formats. These capabilities apply to the documented MCP interface; the consumer apps have separate access conditions.
An image URL, a video task ID and a music result URL require different handling in an agent application. The checked media documentation did not publish one fixed tariff covering every image, video or song request; upstream model prices have not been substituted for an ATXP price.
ATXP separates creating an identity from using it to authenticate requests. Its documented registration and quickstart paths are:
npx atxp agent register.The connection string authorizes account usage. Consolidating access to upstream services under an ATXP account changes how requests are authenticated and paid; it does not remove authentication from the application. The proxy's spending authority is a particularly consequential example, covered under Limitations.
ATXP's search examples cover current-news research and discovery of MCP servers, with results containing a title, URL, text and publication date.
The Crawl service extracts information from websites and can crawl up to a specified maximum number of pages.
Filestore can store, retrieve and delete files; a write request accepts base64 content or a source URL and includes a flag controlling whether the file is public. The documentation presents saving and reading a file between conversations as a use case. File persistence and public exposure are therefore explicit parts of the service interface.
The quickstart supplies curl, JavaScript and Python examples for inference, alongside a Claude Code plugin marketplace route for using tools.
MCP Proxy automatically pays from the connection-string account for clients without native payment support, and currently supports only ATXP-provided MCP servers. It handles payment on the account's behalf, but its documented server scope is narrower than the general ecosystem of paid MCP services.
The following public entrance conditions were captured on October 23, 2026:
| Application | New-account access | Existing-account statement |
|---|---|---|
| ATXP Pics | No longer accepting new signups | Existing accounts can sign in and keep creating |
| ATXP Video | Closed to new signups | Existing users can access their conversations and videos |
| ATXP Music | No longer accepting new accounts | Existing users are told their songs remain available |
The Video statement preserves access to existing material without explicitly promising new generation. Music refers to existing songs rather than expressly describing continued generation. Pics explicitly says existing users can keep creating. These app entrances qualify the main site's continuing promotion of the media products.
ATXP Chat advertises $3 in credit for new accounts without a credit card, switching models mid-conversation and real-time shared chats in which each person pays for their own messages. This consumer offer is separate from the $5 starter-credit package documented for agent accounts; neither figure establishes a universal grant for every ATXP account type.
ATXP's gateway bills for tokens consumed and charges the account balance; current model prices are exposed through the models endpoint. Token-priced inference uses a different billing unit from an email or a paid MCP tool call. A single shared balance does not mean a single flat charge for every operation.
| Email operation | Published charge |
|---|---|
| Check inbox | Free |
| Read message | Free |
| Send email | $0.01 per email |
One IOU equals one USD; ATXP describes IOUs as an internal credit balance rather than a stablecoin or on-chain asset, and says they do not expire. Product usage draws down this balance. A wallet address and an IOU balance are related parts of the account offering, but the IOU itself is described as credit.
The MCP package README describes self-registration through atxp_register as including 10 IOU tokens to start. That differs from the developer CLI documentation's $5 account package, while Chat advertises its own $3 new-account credit. These published starter offers are not a consistent, platform-wide entitlement, and the documentation does not reconcile them.
Unused ATXP balance is non-refundable and carries forward indefinitely. Non-expiry preserves credit for future use; it does not create a refund entitlement.
The funding guide describes Stripe checkout accepting Visa, Mastercard, Amex and Discover, plus USDC deposits on Base and Solana through a support-provided deposit address.
The CLI fund command displays supported USDC funding options and, for agent accounts, a shareable Stripe payment link; the example payment-link output shows a suggested $10.00 with a range of $1 to $1000. That example describes a payment link rather than a universal minimum account balance or a monthly plan.
Auto top-up monitors the balance and triggers a card charge below a user-set threshold, with the reload amount and payment method configured on the Fund page. An enabled reload can replenish the account automatically. The balance available at one moment and the total card charges created by repeated reloads are different quantities.
For a crawl of a website using Cloudflare pay per crawl, the tool-call cost includes the content provider's added fee.
The Terms grant access to the services, including Developer Tools and Mini Apps, solely for personal noncommercial use. This sits alongside the developer offering's explicit promotion of monetized MCP tools and pay-per-call revenue. The two published statements have different implications for commercial adoption, and neither has been substituted for the other here.
For Developer Tools, an accompanying license takes precedence in a conflict, except that Beta or prerelease tools cannot be relied on for commercial or production purposes; open-source provisions may expressly override the Terms. This exception has a defined scope, rather than extending an SDK license to every hosted service or consumer app. The checked Terms do not give a simple platform-wide commercial-output ownership guarantee.
The Terms restrict automated agents or scripts from producing multiple accounts or generating automated searches, requests or queries, with a conditional exception for public search engine indexing under robots.txt parameters, excluding caches and archives. This restriction and its indexing exception appear alongside documentation promoting agent self-registration and programmatic tool requests. Those published statements remain in tension; the restriction has not been interpreted away as applying only to an unrelated use.
The privacy policy lists inputs, outputs, photos, images, music, videos, messages and associated metadata as collected user-generated content, along with blockchain activity and wallet-balance data.
The policy permits sharing with service providers and user-designated third parties, and says payment information is processed directly by processors including MoonPay. This disclosure and the funding guide's Stripe checkout description are separate pieces of the payment documentation. The policy does not describe every transaction as using one named processor.
Connecting a linked service authorizes transmission of data to and from it, while public blockchain interactions may expose transaction information and allow a pseudonymous address to be linked to a person through external sources.
The policy permits service improvement and analytics as well as marketing and advertising, including interest-based advertising data sharing. In the Terms and privacy policy checked for this profile, model-training use or a platform-wide exclusion of inputs and outputs from training was not stated separately. An underlying provider's data promise has not been expanded into an ATXP platform commitment.
Personal information may be retained to fulfil collection purposes, legal requirements and fraud prevention, then deleted, anonymized or isolated when no longer required; transfers may go to the United States and other countries. This purpose-based retention statement is separate from image-file and asynchronous-task expiry periods; it does not set one fixed deletion interval for all account data.
A positive account balance does not override a separately configured per-task budget, and a zero balance stops agents without a grace period. The funding guide treats balance and task budgets as independent controls.
The Terms describe Circuit & Chisel's role as software for self-custodied wallets, state that it is not an exchange or licensed broker and say it does not provide investment, tax or legal advice.
Users can delete certain content through their account and request account closure by contacting the company. The wording covers certain content and a closure request; it does not promise immediate removal of every blockchain record, linked-provider copy or retained record when an account closes.