Circuit & Chisel

A named tool catalog plus a custom route. ATXP's catalog of pay per call MCP servers gives an agent web search, crawl, X live search, a filestore, image, music and video generation, sandboxed code execution, contact lookup, x402 payments and email it sends and receives from its own address; the ATXP client can call any ATXP enabled MCP server, and developers can put their own MCP servers behind per call payment.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Tools, Email, Monetize MCP Tools, @atxp/client)read 2026-09-25

No workflow model. ATXP gives an agent an account, a wallet, a model gateway and paid tools; the agent's own framework (the docs show Vercel AI, Cloudflare Agents, LangChain, CrewAI and the OpenAI Agents SDK) decides the steps. The payment lifecycle it manages is not multi step agent execution.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Build Agents, SDK overview)read 2026-09-25

No retrieval structure over the customer's knowledge. The search, crawl and X search tools query the public web, not the customer's corpus, and the filestore is file storage without indexing or retrieval.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Tools)read 2026-09-25

Spend constraints and an approval hook, no approval surface of ATXP's own. Pre funded credits (IOU tokens) set a structural ceiling on what an agent can spend, and the ATXP client takes an approvePayment callback that runs before each payment, which the developer can use to auto approve small amounts and send larger ones for confirmation. The confirmation step itself is the developer's code.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (@atxp/client) and atxp.ai/llms.txt (IOU tokens and spending limits)read 2026-09-25

No access model and no compliance posture. Each agent gets its own account with a connection token, a wallet and an email address, which isolates credentials per agent but documents nothing about who inside the customer's organization can do what: no roles, SSO or permissions for the account portal. No attestation or trust page is published. Per agent accounts and connection tokens are agent identity, not an access surface for people.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Agent quickstart, CLI, troubleshooting)read 2026-09-25

Transaction history, not a run trace. npx atxp transactions lists an account's recent payments, the account portal shows usage and balance, and the client's onPayment and onPaymentFailure callbacks let a developer record each payment. That reports what was paid for, one payment at a time; nothing shows an agent's steps or tool calls as a run.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (CLI, @atxp/client, Account Portal)read 2026-09-25

A store the agent keeps across sessions, not a memory layer. The Filestore MCP server lets an agent store, retrieve and delete files under its own account, and its inbox keeps mail it can read later, so an agent can carry material from one session to the next. No scope, lifetime or review surface is stated, and the filestore is plain storage the agent reads.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Filestore, Email)read 2026-09-25

Hosted only, with no region or customer environment named. ATXP's gateway (llm.atxp.ai), tools and accounts run as ATXP's hosted service. The Redis and SQLite packages store OAuth tokens for a developer's own paid MCP server, which is the developer's deployment, not ATXP's.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (@atxp/redis, @atxp/sqlite, LLM Gateway)read 2026-09-25

No prebuilt agents or templates are offered for a buyer to adopt. The ATXP Skill gives an existing agent access to the paid tools, a tool bundle rather than an agent. The consumer apps atxp.chat, atxp.music and atxp.pics are built for people, and clowd.bot (beta) hosts OpenClaw, an open source runtime ATXP did not build.

SourceATXP by Circuit & Chisel, atxp.ai and docs.atxp.ai llms-full.txt (ATXP Skill)read 2026-09-25

Work reaches ATXP only when the agent calls the gateway or a tool. Each agent has an inbox at its own address, but the docs show the agent checking it on request; no event, webhook or schedule starts the agent when mail arrives.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Email, CLI)read 2026-09-25

The caller chooses the model. ATXP's LLM Gateway at llm.atxp.ai/v1 is OpenAI compatible and serves GPT, Claude, Gemini, Llama, Qwen and other models from a published catalog with per token pricing; the model is named on each request, and desktop apps such as Goose use it as a provider.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (LLM Gateway, Available models and pricing, Use the LLM Gateway in apps)read 2026-09-25

Documented SDKs and a CLI for ATXP itself. The API reference covers @atxp/client, server, express, base, common, redis, sqlite and solana packages; the CLI registers and funds agents, checks balances, lists transactions and calls tools; the gateway is an OpenAI compatible HTTP endpoint; and the docs are served as an MCP server. SDKs and reference servers are published at github.com/atxp-dev.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (API Reference, CLI) and docs.atxp.ai/llms.txtread 2026-09-25

No evaluation surface for agents. ATXP documents accounts, payments, a gateway and tools; nothing tests or scores agent output. The company's Pareto benchmark harness on GitHub belongs to Unbiased, its separate model product, and a vendor's benchmark of its own model is marketing either way.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt and circuitandchisel.comread 2026-09-25

No agent operates a browser or desktop. The Crawl tool fetches web pages as one of the paid tools, and the code tool runs code in a sandbox.

SourceATXP by Circuit & Chisel, docs.atxp.ai llms-full.txt (Crawl, Code)read 2026-09-25