Home / Token cost / Agentpay

The Agentpay MCP server costs 1,858 tokens before the first call.

Connect Agentpay and its 17 tool definitions are loaded into the model's context on every request — 0.9% of a 200k window spent before your agent does anything.

QUICK ANSWER The Agentpay MCP server's tool definitions consume 1,858 tokens — around the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 17 tools · 1,858 tokens · 0.9% of 200k · 0.2% of 1M Method →

What that buys before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 0.9%
1M WINDOW 0.2%

Corpus context: Agentpay ranks #1625 of 3,213 measured MCP servers by definition cost. The median is 1,905 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own.

Where the 1,858 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 109 tokens per tool.

ToolCategoryTokens% of server
save_recipient Write 219 11.8%
pay_person_clp Financial 186 10.0%
create_card Write 185 10.0%
pay_checkout Financial 172 9.3%
pay_merchant_clp Financial 164 8.8%
fill_card Write 107 5.8%
create_api_key Write 100 5.4%
agentpay_signup Write 97 5.2%
revoke_api_key Destructive 88 4.7%
list_transactions Read 82 4.4%
get_card_details Read 79 4.3%
close_card Write 75 4.0%
check_balance Read 69 3.7%
detect_checkout Read 68 3.7%
list_api_keys Read 62 3.3%
check_account Read 55 3.0%
list_recipients Read 50 2.7%

Most agents use a handful of these tools. They pay for all 17.

A PolicyLayer grant exposes only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. Estimates below assume typical-weight tools (109 tokens each).

Grant scopeDefinition costReduction
All 17 tools (no gateway) 1,858 tokens
3 granted tools ~328 tokens −82%
5 granted tools ~546 tokens −71%
10 granted tools ~1,093 tokens −41%

Agentpay token-cost questions.

How many tokens does the Agentpay MCP server use?+

Its 17 tool definitions total 1,858 tokens — 0.9% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does Agentpay consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce Agentpay's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Agentpay to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 328 tokens, a 82% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

How these numbers were measured.

01
Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02
Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03
Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 07-06-2026 from the PolicyLayer scan database over all 17 catalogued Agentpay tools. Counts refresh with every site build.

Expose only the tools you use — the rest never enter your context.

A PolicyLayer grant scopes Agentpay to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.