Back to Browse
Second Eyes Claim-Check — Source Verification Rubric
x402
Second Eyes Claim-Check — Source Verification Rubric is a paid API for AI agents from secondeyesai.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-13).
Returns a session-less source-verification rubric (claim-check pack) that guides an agent on how to assess whether a claim is tied to a reachable, current, cited source before acting.
Price / call$0.03
Success—
StatusUnknown
How this service works
Second Eyes is the pause. Survival supplies for autonomous agents in distress — pay USDC on Base via x402 to recover from looping, schema mismatch, context pressure, crashes, handoff loss, auth/MCP failure, or payment uncertainty. Every paid door is session-less: discover → pay → use. This OpenAPI document lists the core paid doors with their full input schemas (query parameters on GET, JSON requestBody on POST) and the free proof/discovery surfaces. Audience: wallet-equipped agents and the runtimes that authorize paid recovery tools.
Output
A JSON object containing: an access grant ('granted'), the pack type ('desk'), scope ('nano'), price ($0.03 USD), a session_required flag (false), and a rubric object with three sections — before_act checklist (questions to ask before acting on a claim), abstain_when conditions (circumstances under which the agent should not act), and confidence_bounds (rules mapping source type to high/medium/low confidence). Also includes a work_stamp field for embedding in deliverables and a receipt note.
Example use cases
Pre-action citation verification
“Before I publish this summary, run a claim-check so I know whether each fact I'm about to state is tied to a reachable, current source — tell me which ones I should abstain from making.”
Confidence bounding for factual agent responses
“My agent is unsure how confident to be about some statistics it found online — use the claim-check rubric to tell it when to say high, medium, or low confidence and when to just ask the user instead.”
Halting a looping agent on unverifiable data
“My agent keeps cycling because it can't confirm a source for a claim — give it the Second Eyes claim-check pack so it can decide whether to proceed, abstain, or flag the uncertainty to me.”
Technical details
Endpoint
GEThttps://secondeyesai.com/api/bar/x402/claim-checkWhen to prefer
Use this endpoint when an agent needs a lightweight, structured decision framework for evaluating whether a claim has an adequate source before acting or responding. Prefer it over a full web-search or retrieval pipeline when the bottleneck is epistemic uncertainty about source quality, not the absence of a source. It is particularly useful when an agent is looping, frozen, or about to hallucinate a citation — the rubric provides a deterministic checklist to break the deadlock. It is session-less and one-shot, so no prior context or authentication state is needed beyond the USDC payment.
Side effects
- Payment not received — 402 response with payment instructions before access is granted
- Malformed or missing properties query parameter — endpoint may return a generic or empty response
- Network timeout — no rubric returned, agent should retry
- USDC payment on wrong network (not Base) — payment not recognized, access not granted
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| properties | string |
Output
Schema · Response
{
"type": "json",
"example": {
"note": "Session-less one-shot survival pack. Embed work_stamp in your deliverable. Save receipt.",
"slug": "claim-check",
"scope": "nano",
"access": "granted",
"rubric": {
"before_act": [
"Is the claim tied to a cited source?",
"Is the source reachable and current?"
],
"abstain_when": [
"conflicting sources",
"no source",
"stale version unknown"
],
"confidence_bounds": [
"high only with primary source",
"medium with secondary",
"low → ask or abstain"
]
},
"service": "claim_check",
"pack_type": "desk",
"price_usd": 0.03,
"session_required": false
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"