Extract claims
extract_claimsSplit a text (for example an AI-generated answer) into atomic factual claims. Each claim includes span, grounding_required, claim_type (number|date|quantity|quote|named_entity_fact|comparison|opinion|prediction|other), check_worthiness (high|medium|low), and the source sentence. Hedges are stripped, pronouns are resolved across sentences, and compound sentences are split. Questions, greetings, opinions and predictions are marked grounding_required false. Up to 3 checkable factual claims (opinions skipped) get a next_step: a ready-to-send quick_check request ($0.15, fast verdict with 1-2 sources), with deep_verify ($0.75) and verify_claim ($1.00) bodies in next_step.alternatives, so you can check them in one more call. Price: $0.05 USDC on Base per call via x402; this MCP call returns payment instructions and POST /v1/extract_claims returns the claims. Read-only.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"text": "<text>"
},
"name": "extract_claims"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The text to split into claims, for example a chatbot answer. Up to a few thousand characters. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tool | Yes | Tool name. | |
| result | No | Paid result: { claims: [{ claim_id, text, span, grounding_required, claim_type, check_worthiness, sentence, sentence_index, next_step?: { tool, why, price_usd, endpoint, method, body, alternatives[] } }], recommended_next_steps: { tool, count, total_price_usd, options[] }, summary, priced_usd }. | |
| status | Yes | payment_required: pay the HTTP route with x402 to get the result. ok: result is included. | |
| message | Yes | Human-readable summary. | |
| payment | No | Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402. |