Obolus
HomeResearchCreatorsDemoDocsRun research

OBOLUS DOCS / TESTNET RESEARCH PAYMENTS

Read the system before you trust the receipt.

Product docs for researchers, creators, judges, and reviewers. Each section is split into its own page so the flow is easy to audit.

Start readingRoot architecture

Sections

Product manual

The docs are organized by user job: ask a question, onboard a source, verify a payment, and audit the security model.

Start here

What Obolus does

Obolus answers questions by paying creator-owned context assets when the agent reads and cites them.

For askers

How to run a query

Use the research front door to ask a question, choose a budget, and watch the payment trace.

For creators

How creators get paid

Creators register owned context assets, set a toll price, and earn when the agent reads or cites their work.

Money path

x402 tolls and citation royalties

Both access tolls and royalties use the same Circle Gateway x402 purchase path on Arc Testnet.

Integrity

Claims, quotes, and weights

The model may propose attribution, but code verifies quotes and computes contribution weights.

Proof

What a receipt proves

Receipts show decisions and money movement without pretending every nanopayment has its own transaction hash.

Engineering

System architecture

The app is a Next.js and Supabase product built on Circle's Arc nanopayments reference flow.

Threat model

Security and adversarial tests

The prototype is testnet-only, but the money and attribution invariants are treated as real.

Adversarial review

How to test the claims

Use these checks to prove the app is not paying irrelevant sources, inventing quotes, or overstating verification.

Truth in scope

Current limits

The build proves the loop, but open production onboarding needs stronger controls.

Repository-level engineering documents remain in the root: README, Architecture, Adversarial Testing, Security, Notice, and License.