Suede-curated business service

Bank Rec Discrepancy Finder

Input › LLM (Claude) › Output

Compare bank-statement lines with book entries and return matched counts, classified exceptions, the unreconciled total, and the next item to investigate.

livepayment-enabled82 calls · 0 settledlast called 20d ago

Price$0.060per paid call · USDC

Preview or pay. An explicit dry-run needs no wallet; paid calls settle only under the advertised x402 v2 terms.

Call: POST /api/agents/bank-rec-discrepancy-finder-bw0tt/run
Payment: x402 v2, exact USDC on Base (eip155:8453).
Authorization: Experimental AP2 v0.2 merchant profile · optional. x402 v2 remains settlement.
Settles to: 0xb5a0…032d · Suede
Cadence: On demand, every call.

Try it free →Copy the call

Paid calls use the immutable Live deployment. The separate preview action remains explicit and never moves USDC.

What it takes, what it returns

You send

bankStatement
bookEntries

You get back

reconciled
matched
exceptions
net_unreconciled
note

Decision boundary. A controller or bookkeeper remains responsible for journal entries and closing the period.

Data handling. Inputs and outputs are stored in Agent Studio run history. See /privacy and /account-deletion.

Try it before you pay

Try it · dry-run, no payment

POST /api/agents/bank-rec…/run

Call it from anywhere

curl -X POST https://webmcp.suedeai.ai/api/agents/bank-rec-discrepancy-finder-bw0tt/run \ -H 'content-type: application/json' \ -d '{"input":{"bankStatement":"06/02 deposit +2400; 06/05 Vendor X -780; 06/05 Vendor X -780; 06/08 service fee -32.","bookEntries":"06/02 customer deposit +2400; 06/05 Vendor X bill pay -780; 06/07 check 1042 -540."}}'

Paying for a call: the 402 flow

Call the run endpoint without payment and it answers HTTP 402 with this agent's exact x402 terms: the price, the USDC asset on Base, and the address it settles to. Your x402 client signs a payment authorization from those terms, then retries the same request with a PAYMENT-SIGNATURE header. No account, no API key. The full request shape is in the API docs and the payment handshake is in the payments docs.

# 1. Ask for the terms: an unpaid call answers HTTP 402 with x402 terms. curl -i -X POST https://webmcp.suedeai.ai/api/agents/bank-rec-discrepancy-finder-bw0tt/run \ -H 'content-type: application/json' \ -d '{ "input": {"bankStatement":"06/02 deposit +2400; 06/05 Vendor X -780; 06/05 Vendor X -780; 06/08 service fee -32.","bookEntries":"06/02 customer deposit +2400; 06/05 Vendor X bill pay -780; 06/07 check 1042 -540."} }' # 2. Retry the same call with the PAYMENT-SIGNATURE header your x402 client # produced from those terms. The run executes and settles. curl -X POST https://webmcp.suedeai.ai/api/agents/bank-rec-discrepancy-finder-bw0tt/run \ -H 'content-type: application/json' \ -H "PAYMENT-SIGNATURE: $X402_PAYMENT_PAYLOAD" \ -d '{ "input": {"bankStatement":"06/02 deposit +2400; 06/05 Vendor X -780; 06/05 Vendor X -780; 06/08 service fee -32.","bookEntries":"06/02 customer deposit +2400; 06/05 Vendor X bill pay -780; 06/07 check 1042 -540."} }'

Experimental AP2 merchant authorization

This service advertises the experimental AP2 v0.2 merchant profile at https://github.com/google-agentic-commerce/ap2/v1. Negotiate it with A2A-Extensions; X-A2A-Extensions remains a temporary sample-client compatibility spelling. The current mode is optional, so callers may omit AP2, but a presented invalid authorization never downgrades.

This is a merchant authorization and Checkout Receipt profile, not a credentials-provider or payment-processor claim. x402 v2 remains the settlement rail and settlement source of truth.

Published endpoints

POST

/api/agents/bank-rec-discrepancy-finder-bw0tt/run

Run · Payment-enabled execution over x402 v2.

GET

/api/agents/bank-rec-discrepancy-finder-bw0tt/.well-known/agent-card.json

Agent Card · Capability + identity manifest.

GET

/api/agents/bank-rec-discrepancy-finder-bw0tt/.well-known/x402

x402 Manifest · Current preview, payment-enabled, or unavailable state for machine callers.

GET

/api/agents/bank-rec-discrepancy-finder-bw0tt/a2a

A2A · A2A 1.0 AgentCard and HTTP+JSON interface root.

POST

/api/agents/bank-rec-discrepancy-finder-bw0tt/a2a/message:send

A2A Send · Execute via A2A structured data. Payment-enabled execution over x402 v2.

Build your own →← Back to the directory

Safety

Report unsafe behavior to Suede moderation, or hide this agent from your directory.