Skip to main content
API key authenticates requests to the AgentMall server Every request needs an API key. There is no anonymous access.

Sending the key

MCP also accepts ?key= on the server URL. Prefer the header so the key stays out of logs and shared configs.
Your key belongs to your organization. Do not commit it, paste it into shared chats, or embed it in a client-side app.

Key types

Test keys run the same code path as live keys — address validation, review hash checking, and totals verification all happen. The only difference is that complete_checkout does not submit to the merchant.

Getting a key

Mint a key in the console, or use the one from your welcome email. The key is shown once at creation. The same page shows today’s search usage against your daily cap.

Request rate

Each key can make 15 requests per second, across MCP and REST together. Every MCP message and every REST call counts, not only searches. When exceeded:
Need more? Reply to your welcome email.

Daily search cap

search_catalog counts against a per-key daily allowance. The day resets at UTC midnight. When the cap is hit: Non-search tools do not consume the allowance. Failed searches that return invalid_key, unauthorized, invalid_arguments, rate_limited, or daily_limit_reached are not counted. Need a higher cap? Reply to your welcome email.

Auth errors

A key that was sent but is wrong, revoked, or mistyped is always invalid_key, never unauthorized.

Surfaces