x402 Finance · Broker Statement Audit
Analyze broker statement data to identify hidden FX markups and fee structures.
What it does
Analyze broker statement data to identify hidden FX markups and fee structures.
- Verify broker fee transparency for compliance
- Detect undisclosed markup in FX transactions
- Audit trading costs for institutional clients
Ideal buyer
Financial auditors and compliance teams evaluating broker fee structures.
Run this through your governed agent wallet.
- 01Bootstrap AXON once with
npx @axon402/init. - 02Use the AXON runtime MCP tools to
search_x402_servicesorinspect_x402_offerfor this service. - 03Quote, test-buy, then run the governed paid fetch through AXON.
Send this
Prompt for your agent
A natural-language instruction for your LLM agent — with this endpoint exposed as a tool — to call this resource. Not sent to the endpoint; the endpoint consumes the JSON body below.
Pasting this prompt into a raw ChatGPT or unconfigured agent will notexecute the paid endpoint flow. Run it through an agent with the AXON runtime / MCP tools exposed (see “Use with AXON” above) so the 402 challenge, quote, and governed fetch are handled for you.
“Audit this broker statement for hidden FX fees: [paste statement data]”
Endpoint request body
The JSON payload your agent sends to the endpoint.
{
"statementData": "broker_statement_raw_text_or_json"
}Advanced HTTP details
For integrators who need the raw protocol surface. Most agents should use AXON above instead of calling these directly.
Endpoint URL
curl fallback
curl https://x402-finance-api.vercel.app/broker/audit \ -H "Content-Type: application/json" \ -H "X-PAYMENT: [signed_payment_envelope]" \ -d '{"statementData":"broker_statement_raw_text_or_json"}'
Payment & settlement details
Raw on-chain settlement parameters. AXON above handles these automatically through quote / test-buy / governed fetch.
Price & network
Trust & risk
More in Finance
Browse all →Other resources in this category
Category proxy — we don't track live co-purchase signals yet.