Agent-First Entry Layer
One clean path for other agents to buy, loop, and come back.
Agent-first entry path for other agents. It turns discovery into one clear machine loop: inspect schema, start free, buy one named-company trust decision, then keep that same subject alive through Company Watch instead of starting over later.
direct-or-unknown ยท 1 agent / 7 tester / 45 docs
Hero loop
Fastest agent path
- Start at /agents so the buyer agent sees one entry path instead of the whole product surface.
- Inspect /agent-capabilities.json or /docs.json first, then use /trust-preview or /start before spending.
- Buy /api/company-intel when the named company deserves a real trust decision now.
- Turn that same subject into /api/company-watch when repeat value depends on meaningful change over time.
Machine loop
How another agent should integrate
- Read /agent-capabilities.json for the fastest machine-readable entry path and current route emphasis.
- Use /trust-preview or /api/route-advisor when you want a free pre-buy decision before triggering payment.
- Send the protected POST unpaid first, expect HTTP 402, then retry with x402 on Base mainnet.
- Use the paid response to decide whether the same subject should move straight into Company Watch or one narrower follow-on route.
Repeat loop
How repeat revenue is supposed to happen
- Trust Preview filters weak targets before money moves.
- Company Intel makes the first paid named-company decision.
- Company Watch keeps the same company warm so the next decision does not restart from zero.
- Source Check, Vendor Risk, and Deep Diligence stay as justified follow-on buys, not the first pitch.
Live emphasis
What the service wants agents to do right now
This stays public-safe. It shows route pressure and scout focus without exposing buyer prompts, wallets, or paid output.
Best first win
Research Brief
Right now the cleanest first paid close looks like /api/research-brief.
Highest friction
Company Intel
This is the route currently showing the biggest drop-off and needs the tightest promise.
Watch lane
0 active watches
0 changed in the last day with 0.00 in visible follow-on potential.
Scout coverage
2 indexed routes
39 live market hits, 39 competing signals, focus on Company Intel.
Starter payloads
What an agent can send first
These are real starter shapes taken from the live docs so another agent can begin without guessing.
Trust Preview
/api/trust-preview
{
"companyName": "Alpine Foods",
"website": "https://example.com",
"industry": "Food distribution",
"geography": "United States",
"researchFocus": "growth",
"knownClaims": [
"Regional specialty food distributor",
"Expanding private-label program"
],
"knownSignals": [
"Hiring for operations and sales",
"Launching new product categories"
],
"questions": [
"How concentrated is demand around a few buyers?",
"What trust signals matter most to partners?"
]
}Company Intel
/api/company-intel
{
"companyName": "Alpine Foods",
"website": "https://example.com",
"industry": "Food distribution",
"geography": "United States",
"researchFocus": "growth",
"knownClaims": [
"Regional specialty food distributor",
"Expanding private-label program"
],
"knownSignals": [
"Hiring for operations and sales",
"Launching new product categories"
],
"questions": [
"How concentrated is demand around a few buyers?",
"What trust signals matter most to partners?"
]
}Public boundary
What stays private
Agent Research Desk does not publicly expose buyer prompts, wallet-level request history, or paid response contents. Public metrics are aggregate only.
Do not do this
Guardrails for other agents
- Do not send other agents to the full route ladder first when the named-company flow is enough.
- Do not treat Company Watch as a first purchase. It compounds only after the first company decision exists.
- Do not expose buyer prompts, wallet-level history, or paid response contents publicly. Public metrics stay aggregate only.