// TRUST INFRASTRUCTURE FOR AGENTIC COMMERCE
Faro
Is this counterparty real — before value moves?
One engine. Five surfaces. Businesses claim a page and bind their agent; developers verify URLs, payees, and messages via API, MCP, or Apify — same red / yellow / green verdict every time.
Pages · Guard · Index · Keepers · Club · API · MCP · Apify · x402
Google Safe Browsing flags this URL as Social Engineering.
// THE SUITE
Five products. One graph. Zero fake confidence.
Sensors write claim, agent-binding, and verdict edges. Lenses render them. Badges never feed the trust decision — the badge is a mirror, never a lever.
Faro Pages
Claim your entity, prove control, register your business agent, publish live standing.
FaroGuard
Checkout gate that verifies the payee — and who the buyer’s agent acts for. Button stays yours.
Trust Index
Aggregate corridor and sector movement. The index nobody can spin.
Keepers
30-day cohort: claim → wire → register → light it. Stakes = invisibility, never shame.
Verified Club
Paid badge + directory. Longevity you keep green — never buy the Lighthouse.
Build on Faro
Ship adapters & SDKs on the public repo. Engine stays closed; interface is Apache-2.0.
// FOR BUILDERS
Ship a safety check in an afternoon.
Plain HTTP for your backend. MCP for agents. Apify Actor for automation. x402 / Bazaar paywall for unkeyed agent traffic — counsel-gated, in build.
Contribute adapters on GitHub →curl https://api.farofinance.app/v1/verify/url \
-H "Authorization: Bearer $FARO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"value": "http://sbi-kyc-update.xyz/verify"}'
# →
{
"verdict": "red",
"confidence": 0.97,
"reason": "Google Safe Browsing flags this URL as Social Engineering.",
"recommended_action": "block"
}// REGISTER ONCE
Verified everywhere your agent transacts.
Mid-onboarding, bind a faro_agent_ key to your entity. At your checkout and a counterparty's, Faro answers: who does this agent act for, and is that entity real?