WritersLogic Verifiable AI Agent Hub Crosstalk Deliberate API
The Crosstalk Deliberate API from WritersLogic Verifiable AI Agent Hub — 1 operation(s) for crosstalk deliberate.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/writerslogic-com:writerslogic-com-crosstalk-deliberate-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: WritersLogic Verifiable AI Agent Hub Crosstalk Deliberate…
version: 2.0.0
description: Pay-per-call agents settled in USDC on Base via x402. Every response carries a signed provenance envelope.
contact:
name: WritersLogic
url: https://writerslogic.com/agents
email: agents@writerslogic.com
servers:
- url: https://agents.writerslogic.com
tags:
- name: Crosstalk Deliberate
paths:
/api/v1/crosstalk-deliberate:
post:
operationId: crosstalk_deliberate
summary: Crosstalk epistemic swarm & falsification engine
description: 'Stress-tests a research question instead of answering it once. Classifies the domain, generates up to 3 independent hypotheses, attacks each with an adversarial falsification pass, checks live literature on arXiv and OpenAlex (plus any papers you supply by arXiv id or DOI; every record content-addressed by sha256), then synthesizes a calibrated answer. The output leads with a headline (status, answer, confidence, open cruxes) and one decisive falsification probe as the next step. Every material statement is a typed ledger entry (FACT, ASSUMPTION, INFERENCE, CONJECTURE, PROPOSAL) with evidence digests; FACT claims lacking a verified retrieved record are downgraded, invented citations are stripped, and the stage transcript is a recomputable sha256 hash chain. Model-generated reasoning over abstracts, not a systematic review; if synthesis fails you still get the hypotheses and critiques, marked HYPOTHESES_ONLY. Runs in about a minute with 5 to 8 model calls.
Price: 2.00 USDC on Base (x402).'
x-x402-price-usdc: '2.00'
x-x402-amount: '2000000'
x-payment-info:
protocols:
- x402
price:
mode: fixed
currency: USD
amount: '2.00'
x-audience: research
x-sample-url: https://agents.writerslogic.com/api/v1/samples/crosstalk-deliberate
security:
- x402: []
- apiKey: []
requestBody:
required: true
content:
application/json:
schema:
type: object
additionalProperties: false
required:
- question
properties:
question:
type: string
minLength: 3
maxLength: 4000
description: The question or claim to deliberate.
context:
type: string
maxLength: 8000
description: Optional background, constraints, data or prior attempts.
maxHypotheses:
type: integer
minimum: 1
maximum: 3
description: Independent hypotheses to generate and attack (default 3).
papers:
type: array
maxItems: 5
items:
type: string
minLength: 4
maxLength: 200
description: Up to 5 papers you already have, as arXiv ids or URLs (2201.11903, arxiv.org/abs/...) or DOIs (10.xxxx/..., doi.org URLs). They are fetched and become citable evidence records alongside the live literature search.
example:
question: Does chain-of-thought prompting improve accuracy on multi-step arithmetic in large language models, and does the effect persist at larger scale?
context: Interested in published empirical results, not opinion.
maxHypotheses: 2
responses:
'200':
description: Paid result with provenance
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
headline:
type: object
description: 'Verdict-first digest: status (EVIDENCE_BACKED, UNVERIFIED_REASONING, HYPOTHESES_ONLY when synthesis failed, NO_ANSWER), answer, confidence 0-1 and band, openCruxes, a one-sentence summary and the concrete nextStep (the falsification probe when available).'
question:
type: string
domain:
type: string
enum:
- cryptanalysis
- decipherment
- history
- mathematics
- natural_science
- cs_ai_engineering
- debate_decision
- general
llm:
type: string
enum:
- ok
- partial
- unavailable
description: 'partial/unavailable: a model stage failed with a 5xx; deterministic results are still returned.'
conclusion:
type: array
items:
type: object
description: Calibrated answer, as ledger entries.
confidence:
anyOf:
- type: number
description: Mean confidence of the conclusion entries after the evidence caps; null when none.
- type: 'null'
cruxes:
type: array
items:
type: object
description: Open or contested ledger entries the answer depends on.
falsificationProbe:
anyOf:
- type: object
description: The one PROPOSAL ledger entry naming the decisive next experiment, or null.
- type: 'null'
hypotheses:
type: array
items:
type: object
ledger:
type: array
items:
type: object
description: '{id, type, text, evidenceDigests[], confidence, status, evidence[], originalType?}.'
edges:
type: array
items:
type: object
evidence:
type: object
description: Retrieved records with sha256 digests, per-query lookups with response digests and any failures.
transcript:
type: object
description: Stage inputs/outputs, per-stage digests and chainHead; recompute with the stated algorithm.
deterministic:
type: object
description: Ledger discipline adjustments, statistics, coverage, ledgerSha256 and a self-check of the transcript chain.
timing:
type: object
description: elapsedMs and the wall-clock budget the stages were held to.
warnings:
type: array
items:
type: string
analyzedAt:
type: string
_provenance:
type: object
description: C2PA-aligned manifest and W3C VC 2.0 (eddsa-jcs-2022) issued by the hub DID; verify at POST /api/v1/verify-provenance
required:
- data
- _provenance
'400':
description: Invalid request (no payment consumed)
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
'401':
description: Invalid X-API-KEY
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
'402':
description: Payment required or invalid
content:
application/json:
schema:
type: object
description: x402 v2 PaymentRequired (also base64 in the PAYMENT-REQUIRED header)
properties:
x402Version:
type: integer
error:
type: string
code:
type: string
resource:
type: object
accepts:
type: array
items:
type: object
extensions:
type: object
'502':
description: Upstream failure; the payment is released or not settled
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
tags:
- Crosstalk Deliberate
components:
securitySchemes:
x402:
type: apiKey
in: header
name: PAYMENT-SIGNATURE
description: x402 v2 payment payload (base64) sent after a 402 challenge
apiKey:
type: apiKey
in: header
name: X-API-KEY