Integration idea: amount-aware counterparty exposure before payment authorization #55

Hi — MCPay's registry + proxy makes it easy for an agent to find a priced MCP tool and pay for it over x402, with policy-based authorization deciding whether the proxy pays on the agent's behalf.

In the public policy flow we reviewed, we didn't see an evidence-based counterparty input describing how much exposure to a specific seller is supported by observed settlement evidence before payment is authorized.

We built Fidren to answer that question.

Given a counterparty address and a requested amount, Fidren returns:

• a payment action
• supported exposure
• confidence
• reasons
• labelled evidence

The amount matters. With the same counterparty and the same evidence, a $50 request against $100 of supported exposure returned REVIEW, while a $50,000 request against the same $100 of supported exposure returned DO_NOT_PAY_AS_REQUESTED.

Free tier: 100 decisions/day, no account, no API key, no card — one HTTP call.

https://fidren.net/developers

We're not proposing any change to MCPay's proxy or facilitator. The simplest evaluation would be to run Fidren read-only beside the existing policy authorization step and compare whether amount-aware counterparty exposure adds useful information before payment.

If that's interesting, we'd be happy to compare notes from a small sample.