What ATXP enables
ATXP connects agent tools with payment. Providers can offer a paid MCP service, for example, while the client integration handles the associated account and payment flow. The project provides packages for clients, servers and integration into existing applications.
Connections with other protocols
- The MCP integration connects a tool call with the ATXP payment flow.
- The @atxp/x402 package connects to x402. Other packages provide client, server and Express integration.
Versions and licence
- Published version
- No separate version stated
- Working draft
- —
The version numbers below refer to individual packages, not a shared protocol revision.
- Licence / terms
- MIT for SDK and integration packages; separate service terms apply to the hosted service.
Licence and terms ↗
An example flow
- A provider exposes a paid service using the ATXP server integration.
- An agent calls the tool through the corresponding client.
- The integration processes the specified payment requirements.
- The server executes the paid call and returns the result to the agent.
SDKs and examples
These libraries and examples help you get started. Each entry lists the language, package and supported version.
From the protocol projectTypeScript · JavaScript
ATXP SDK
Includes: Client, server and framework integrations
Package / module: @atxp/client; @atxp/server; @atxp/express; @atxp/x402
Version & compatibility: @atxp/client 0.11.12; @atxp/server, @atxp/express and @atxp/x402 each 0.11.11
Practical integration
- @atxp/client, @atxp/server and framework packages each have their own versions. The SDK table lists the packages used.
- The integration connects the provider and client with the account and billing model of the ATXP service being used.