Integrators
Bring the audience. We will do the paperwork.
Aletheca is a foundation. Any site whose readers want a record can embed the whole discipline behind its own buttons, keep its interface and its domain, and take a share of the revenue on every request it originates.
- 01
Agree the terms
Scope, surfaces, and the revenue share rate. The rate is set at integration by agreement rather than by a published grid, because a general-interest news site and a specialist archive are not bringing the same thing to a request.
- 02
Take a signed handoff
A separate operator-issued handoff key lets your server create short-lived hosted composer links. Aletheca verifies attribution and the issuing key before submission; a public slug cannot claim it. The reader still signs in and submits.
- 03
Embed or call
Use the script tag for public status and hosted action links, or render the public REST reads yourself. Writes remain in Aletheca's authenticated composer and checkout.
- 04
Read the ledger
Read keys reconcile exact private references and inspect delivery health. A separate accounting key reads accrued earnings statements. Operator-managed HTTPS receivers can receive signed milestones after worker activation. Self-service receivers and payouts remain planned.
How the share is calculated
The share is a percentage of Aletheca’s own platform fee — the filing and follow-up line, and the embargo surcharge where one applies. It is never a share of postage, print, provider costs, or agency fees.
That boundary is deliberate. Sharing a cut of postage would mean a partner earns more when a request goes certified with a return receipt than when it goes by email, and that is an incentive pointed directly away from the requester’s interest. Pass-through costs pass through.
Prospective accounting accrues only an explicitly classified platform fee after an operator approves the agreement and the payment total is verified. Refunds and disputes adjust the frozen share through auditable entries. Verified discounts reduce the collected share base within their own filing. Historical samples and unsupported payment proof do not create earnings. A separate accounting:read key can retrieve your accrued earnings and adjustments through the API, including complete snapshot downloads within the export limit. Financial dashboard screens, payee onboarding, transfers and payout reconciliation remain planned.
Worked example
- Commission paid by the reader$29.64
- Certified mail + return envelope (pass-through)− $14.64
- Aletheca platform fee$15
- Partner share at 15%$2.25
A portal or email request has no pass-through at all, so the same 15% is $2.25 on a $15 request. The rate is what varies between integrations; the base it applies to never does.
Current integrations
These are the hand-maintained commercial records currently published by Aletheca. They are not a live payout ledger or evidence of an automated transfer.
UAP Nexus uap.nexus
liveThe first integration, and the reason Aletheca exists as its own property. UAP Nexus was going to build a FOIA engine into a sightings catalog; it embeds this one instead, and gets the whole pipeline — drafting, payment, the statutory clock, publication — behind its own buttons.
- Case pages carry a 'Request the records' button that opens the composer pre-filled from the case
- A campaign panel on the disclosure timeline
- The Docket embedded at /foia, filtered to UAP subjects
Share 15%Originated 41 requestsRecorded accrual $384Since Mar 1, 2026Mysteria mysteria.co
buildingSite-monument records held by state historic preservation offices. Different statutes, same machine.
- Place pages requesting heritage-agency survey and excavation records
Share 15%Originated 0 requestsRecorded accrual $0Since Sep 1, 2026Libra Esoterica libraesoterica.com
prospectiveProvenance files on manuscripts whose ownership history has a hole in it.
- Requests for institutional provenance files on contested manuscripts
Share 15%Originated 0 requestsRecorded accrual $0Since Jan 1, 2027
What we ask in return
The response is published
Whatever it says. A partner cannot embed the pipeline and then ask for an unflattering release to be suppressed — the archive's third clause is not negotiable per integration.
The refusal policy applies
Requests originated through your site pass the same review gate, including the rule against targeting private individuals.
Attribution runs both ways
Your site is credited on every request it originates, permanently and publicly. In exchange, link the request page rather than reproducing the ledger as your own.
Ready to talk? hello@aletheca.com · Read the embed guide first if you want to know what it looks like on the page.