California Bitcoin for agents

Start with a free source-backed Bitcoin answer.

Give California Bitcoin the real Bitcoin question first. The free Start Here call returns a deterministic answer, checks maintained coverage, and recommends the smallest safe next action. Pay only when the task genuinely needs evidence-grade verification, packaging, chronology, or deeper grounding.

Run Start HereCapability indexOpenAPI 3.1A2A Agent CardMachine manifestMCP manifestllms.txt

Delegate Bitcoin research agent to agent.

A2A 1.0 · synchronous JSON-RPC
Grounded research

Delegate a Bitcoin question.

A general-purpose agent can hand California Bitcoin a focused question and receive a direct source-backed structured response from the maintained knowledge system.

Primary sources

Ask what a historical source actually said.

Covered attribution questions use retained, integrity-checked primary-source dossiers. Uncovered attribution fails safely instead of substituting a generic topical answer.

Evidence state

Check prior evidence before repeating work.

Agents can compare a retained evidence checkpoint for free before deciding whether research needs to be rerun.

A2A v1 endpoint: /a2a. It is intentionally synchronous and free. It does not advertise persistent tasks, streaming, push notifications, or paid A2A execution. Evidence-grade paid research continues through the existing MCP and HTTP Stripe MPP interfaces.

Try California Bitcoin now.

Live free calls, safe paid previews
Free operations call the live public API. Paid previews never initiate payment.
Run a free call to inspect the live structured response.


  
Use it when a Bitcoin answer needs evidence, not another search result.
Maintained, deterministic, primary-source-first
Verification
Is this Bitcoin claim actually supported?
Adjudicate a proposition against maintained evidence, including contradictions, caveats, source authority, locators, and temporal context when available.
Evidence
Give another agent auditable support.
Retrieve structured Bitcoin evidence and provenance with exact locator-backed support distinguished from broader source-level support.
Chronology
Build a sourced Bitcoin timeline.
Use maintained historical relationships when the sequence of protocol, technical, or historical events matters.
Grounding
Ground a broader Bitcoin research task.
Assemble deterministic multi-topic context when a generic web research agent needs a Bitcoin-specific evidence layer before acting downstream.


  
Start free. Pay only for research.
Server prices are authoritative
Start Here / Search / Topic / Ask / Coverage / SelectionFree
Discover scope, retrieve canonical knowledge, inspect source quality, and choose the right product before spending anything.
Verify Claim / Evidence Pack / Timeline$0.10 / $0.15 / $0.10
Use when a workflow needs adjudication, a structured evidence set, or source-backed chronology.
Deep Ground / Batch$0.25 / $0.50
Use for multi-topic dossiers or up to 20 claims and questions in one research package.


  
Canonical demonstration problems.
24 high-value research cases
These are designed to expose the difference between generic retrieval and maintained Bitcoin verification. Each can be evaluated through the free layer before an authorized agent chooses a paid research product.
Loading demonstration catalog…


  
Product selection is explicit.
Selection never authorizes payment
HTTP
Deterministic routing
POST /api/agent/v1/select-product
Content-Type: application/json

{"task":"verify"}
Tasks are verify, evidence, chronology, dossier, batch, and learn. The response explains purpose, exact price, input, output, when not to use the product, and the free alternative.
MCP
Same decision through MCP
Tool: select_bitcoin_research_product
Arguments:
{"task":"evidence"}
The selector is free and read-only. Product choice and permission to spend are separate decisions.


  
Copy, paste, integrate.
Standards first, no SDK required
curl
Free deterministic answer
curl -X POST https://californiabitcoin.org/api/agent/v1/answer \
  -H "Content-Type: application/json" \
  -d '{"query":"What does a Bitcoin full node verify?"}'
JavaScript
Free canonical search
const r = await fetch(
  'https://californiabitcoin.org/api/agent/v1/search?q=proof%20of%20work'
);
const result = await r.json();
MCP
Remote Streamable HTTP
Endpoint: https://californiabitcoin.org/mcp

Free tools:
search_bitcoin_knowledge
get_bitcoin_topic
answer_bitcoin_question
select_bitcoin_research_product
Autonomous agent
Generic workflow
1. Search or inspect coverage for free.
2. Inspect provenance and source quality.
3. Select a product for the task.
4. Confirm the exact server price.
5. If authorized, handle the MPP 402 challenge.
6. Reuse the structured evidence downstream.


  
Paid calls use Stripe MPP inline.
HTTP 402 is part of the protocol
1
Send the exact paid research request.The server validates the input before asking for payment.
2
Receive 402 Payment Required.Read the WWW-Authenticate: Payment ... challenge. It contains the server-selected amount and a request-bound payment challenge.
3
Fulfill the challenge with an MPP-capable payment client.California Bitcoin never trusts a caller-provided paid flag, price, or receipt.
4
Retry the identical request with the payment credential.The server verifies the challenge and confirms Stripe settlement.
5
Receive deterministic research plus payment and trust receipts.Exact retries are idempotent and do not create a second charge.
curl -i -X POST "https://californiabitcoin.org/api/agent/v1/verify-claim" \
  -H "Content-Type: application/json" \
  -d '{"claim":"Bitcoin has no central issuer"}'

# First response: HTTP 402 with a Payment challenge.
# Fulfill it only with spending authorization, then retry the identical request.


  
Every paid result carries a compact trust receipt.
Evidence summary, not a signature
The trust receipt helps another agent judge a result without duplicating the full research payload. It distinguishes source-level citation readiness from the stronger exact-locator-backed state. Payment does not guarantee coverage, exact locators, independent confirmation, or a favorable verdict.
Verdict + confidenceDeterministic evidence alignment, not calibrated probability
Engine + graph versionsResearch Engine and Fact Graph used for the result
Evidence + source countsDescriptive totals, not counts of independent confirmations
Citation precisionSource-level support versus exact maintained locators
Contradictions consideredConflicting maintained claims are counted explicitly
Temporal statusasOf and reverifyAfter when evidence is version-sensitive
Deterministic result IDStable result identity for identical deterministic work
Canonical endpointWhere the research product was produced


  
Agent onboarding in nine steps.
From discovery to reuse
DiscoverFind the MCP, OpenAPI, llms.txt, or developer surface.
UnderstandRecognize verification and evidence as the core job.
Evaluate freeSearch, ask, inspect coverage, or retrieve a canonical topic.
Inspect provenanceCheck source authority, locators, caveats, and maintained versions.
SelectUse the free product selector for the research task.
Confirm priceRead exact server pricing before any payment attempt.
Pay when authorizedFulfill the Stripe MPP challenge and retry the identical request.
Receive evidenceUse deterministic structured research plus the trust receipt.
Reuse downstreamPass structured evidence into the next agent or workflow.


  
When California Bitcoin is the wrong tool.
Use the narrowest authoritative system
Use a market-data API
For live Bitcoin prices and rapidly changing market quotes.
Use a node or chain API
For current transactions, balances, blocks, mempool state, and fee estimates.
Use current primary sources
For breaking developments that have not yet entered the maintained evidence layer.
Use ordinary search first
For broad web discovery. Call California Bitcoin when a specific Bitcoin proposition needs source-backed verification or structured evidence.


  
Privacy: California Bitcoin machine telemetry records operational fields such as product, response status, payment status, latency, and payment reference. It intentionally does not fingerprint agents or store prompts, request bodies, IP addresses, user agents, or payment credentials.