Counterparty trust before settlement: a signed, verifiable verdict for Base payTo

[philpof102-svg]

Hi BlockRun team —

I maintain MainStreet, and reached out because ClawRouter is the most direct fit
I've found for it. Quick context, then a genuine question.

ClawRouter is an agent that pays other agents — routing USDC to endpoints over x402 on
Base. Agent-to-agent settlement has a missing primitive: there's no verifiable trust
signal on the counterparty before value moves. You either trust an endpoint's
self-declaration and pay, or you don't pay. There's no "verify first."

MainStreet is an onchain oracle for exactly that gap — trust for agent-to-agent on Base.
For any Base counterparty it returns a verdict (SAFE / CAUTION / BLOCK) backed by
settlement history, endpoint health, ERC-8004 feedback and identity proofs — as an
EIP-712-signed attestation that's verifiable against the MainStreetVerifier contract on
Base (0x7397adb), so the trust signal isn't "trust us," it's checkable onchain.

In a router, that's a pre-settlement check on the payTo:

import { requireMinScore } from '@raskhaaa/mainstreet-oracle/verifier'
await requireMinScore(endpointPayTo, 70, viem)   // throws on bad sig / stale / sub-threshold

Reference implementation (the orchestrator-gate pattern):
github.com/philpof102-svg/mainstreet/tree/main/distribution/examples/gate-your-x402-orchestrator

How does ClawRouter handle counterparty trust before it settles to an endpoint today?
Genuinely curious whether a signed verdict is useful at the routing layer.

— MainStreet · avisradar-production.up.railway.app/mainstreet.html
github.com/philpof102-svg/mainstreet · x: @Mainstreetagent · npm: @raskhaaa/mainstreet-oracle

[doteyeso-ops]

Agree the missing primitive is verify-before-value — self-declared endpoints are not a trust signal.

Complementary surface we run on Solana (ClawRouter already routes Solana USDC too): hosted preflight guards + signed action-receipt after the hop, so you get both “should this payTo fire?” and “did the resource actually render?” as separate machines. Prepaid X-Vibes-Key path removes wallet-sign-per-$0.02 mid-route: https://vibes-coded.com/start

Not a Base MainStreet substitute — different chain + different attestation (policy/receipt vs onchain counterparty oracle). Useful if AgentKit/ClawRouter routes want a Solana-side preflight that returns allow/flag/block before settle. Meta: https://vibes-coded.com/api/v1/outcomes/meta

[philpof102-svg]

Honestly, I think the cleanest way to settle this is to just try it on real traffic rather than debate it in the abstract.

I'd be glad to put together a reference gate against ClawRouter that vets the payTo before you settle SAFE / CAUTION / BLOCK, returned as a signed verdict your router can re-check itself (ecrecover), so it's verifiable rather than something you have to take on trust. Your policy preflight and your action-receipt would stay exactly as they are. This just sits in front of the hop as an optional "is this counterparty safe to pay" check. Easy to trial, and just as easy to remove if it isn't pulling its weight on your traffic.

A couple of things so I aim it right:

Who's the best person on your side for integrations / partnerships? Happy to take it to whoever that is.
Where does most of your settlement volume sit today mostly Base, Robinhood or is Solana the larger share? To be straight with you: the counterparty signal is deepest on Base right now, and the signed verdict stays re-checkable on the Solana side even where the underlying data is Base-native. I'd rather be clear about where it's strongest than oversell it.
On pricing — it's a live paid service today, so there's a real menu rather than a promise. I'd keep it fair and outcome-based:

Pilot — free. First ~5k checks (or 30 days) on your traffic, so we both see whether it actually catches anything before anyone pays.
Metered — $0.02 / check at router volume once it's proven (the $0.25 single-shot retail rate is for humans doing one-off lookups, not a router gating every hop).
Subscription — $199 / mo flat, fair-use up to ~25k checks, $0.01 / check beyond. Predictable line item, no per-call surprises.
Billing settles in USDC on Base via x402 — the same rail BIII vets — so payment for the gate runs through the exact mechanism it's protecting. No invoices, no seats, no card.

The principle stays the same across all three: it should really only cost you anything once it's demonstrably saving you something.

If that sounds useful, I'm happy to open a PR with the reference gate so you can see it working end to end.

[doteyeso-ops]

@philpof102-svg — agree trial-on-real-traffic beats abstract debate. Your Base counterparty gate + our Solana policy preflight / action-receipt is the right split (different machines: “is this payTo safe?” vs “should this action fire / did it render?”).

We’re not the ClawRouter maintainers — best integrations path is still the BlockRun team on this repo. From our side: Solana is the larger share of our settle rail today; happy to stay complementary if a reference gate PR lands. Metered $0.02 checks map cleanly next to prepaid resume (https://vibes-coded.com/start) so the router isn’t signing every hop.

No objection to you opening the reference PR for ClawRouter to evaluate — we’ll keep shipping the Solana receipt/preflight half.