verified_route

Paid buyer-side trust oracle:

Category Read
Risk class Low
Parameters 00 required

What verified_route does on AgentPay x402 — Economic-intelligence layer for AI Agents

AI agents call verified_route to retrieve information from AgentPay x402 — Economic-intelligence layer for AI Agents without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why verified_route needs a policy

The tool appears to check or verify routing information, which is a read operation. While it is part of a financial platform (AgentPay on Stellar) and costs USDC to call, the tool itself does not move money, execute trades, or modify state — it only provides data to inform decisions. The 'buyer-side trust oracle' framing suggests it returns trust metrics or verification status for routes.

From the tool's definition Tool name is 'verified_route' and described as a 'Paid buyer-side trust oracle' — it queries or retrieves trust/verification data for routes.

Questions about verified_route

What does the verified_route tool do? +

Paid buyer-side trust oracle:. It is categorised as a Read tool in the AgentPay x402 — Economic-intelligence layer for AI Agents MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on verified_route? +

Register the AgentPay x402 — Economic-intelligence layer for AI Agents MCP server in PolicyLayer and add a rule for verified_route: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AgentPay x402 — Economic-intelligence layer for AI Agents. Nothing to install.

What risk level is verified_route? +

verified_route is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit verified_route? +

Yes. Add a rate_limit block to the verified_route rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block verified_route completely? +

Set action: deny in the PolicyLayer policy for verified_route. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides verified_route? +

verified_route is provided by the AgentPay x402 — Economic-intelligence layer for AI Agents MCP server (romudille-bit/agentpay). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

verified_route is one line of AgentPay x402 — Economic-intelligence layer for AI Agents's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.