Public-record Evidence Bundles

Understand the coverage

The bundle reflects records available in the provider index when it is prepared. Coverage and source dates vary; a company's ticker or CIK does not establish a match across every source.

Company bundles may include up to 25 eligible SEC filing records from a 365-day window, available OFAC civil-enforcement references and qualified CISA candidates. Mine bundles contain up to 250 indexed citations for one exact mine ID, subject to the displayed size cap. Mine results are a historical sample, not a latest-first feed or a complete safety assessment. Ingestion dates are shown; they do not promise current coverage.

Review the resolved identity, listed coverage and any unavailable or unmatched sources in the preview and result. A missing record or no match is not clearance, a complete investigation or evidence that an event never occurred.

The price covers this service, not exclusive rights to underlying records. Source-specific licenses and terms apply.

Used the export for a real research task? Tell us what work it replaced and what was missing. Describe the task using public information; keep private payment files and credentials out of feedback.

Prepare a free preview

Select a product and check the identity, record count and source dates in its free preview before paying.

Try an example: Apple (AAPL) · Western Proppants Facility #1 (4801833). Links fill the form; choose Prepare free preview to request the records.

Previews are saved on this browser profile so you can return to the same job. Preparing a preview never connects a wallet or authorizes payment. Keep this browser's data and any private payment backup; another profile cannot see its saved attempts.

Open a private payment backup

Reopen a downloaded payment record to export its saved evidence or recover the original result. Opening the file happens locally; it does not upload the backup or connect a wallet.

Use ai-analytics-private-payment.json from browser checkout, smaller than 1 MiB. Preview-only files and command-line journals are not supported here. Keep the original file private.

Developer guide

OpenAPI specification · AI client guide · Buyer client checksum

Run the buyer client

Download one file and run it with Node.js 22 or newer on macOS or Linux. Its payment libraries are included. No repository access, package installation or API key is needed for the free preview.

Download buyer.mjs · Client license and dependency notices

curl --fail --proto '=https' \
  https://api.ai-analytics.org/paid/client/buyer.mjs \
  --output buyer.mjs
node buyer.mjs --help
node buyer.mjs --product mine-records --mine-id 4801833

For a company, run node buyer.mjs --identifier AAPL --expected-name "Apple Inc.". The client prepares its own job, prints the preview and checks the exact payment terms. This first run does not sign or pay. To inspect the download, compare shasum -a 256 buyer.mjs with the SHA-256 in the release manifest.

After reviewing that offer, an explicit --pay permits one $0.02 native-USDC payment attempt on Base. Supply your buyer wallet key through your local secret manager as EVIDENCE_BUYER_PRIVATE_KEY; never paste a key into this website, a command argument or a support message.

node buyer.mjs --product mine-records --mine-id 4801833 --pay

Use the same product arguments and keep the downloaded file in the same directory. The client saves private journals in evidence-live-receipts/ beside it, including the result and recovery capability when delivered. It refuses another purchase after a signed or uncertain attempt. Keep that directory; moving the client or deleting its journal can lose its duplicate-payment protection. A checksum identifies the release bytes; it does not prove a purchase or settlement.

Use your purchased records

With the same product arguments, export a retained result to JSON and spreadsheet-ready CSV files. This command works locally, including after the purchase quote or recovery token expires.

node buyer.mjs --product mine-records --mine-id 4801833 --export

You receive the original bundle, record and source tables, coverage metadata and a checksum manifest. Mine exports also include an annual summary of the delivered citations, with separate proposed-penalty and reported-payment totals and missing-value counts. These are summaries of the saved sample, not a complete mine history or an outstanding-debt calculation.

If the journal retains a valid recovery token but needs the result again, retrieve and export that original artifact with:

node buyer.mjs --product mine-records --mine-id 4801833 --recover

Recovery makes one authenticated GET and checks the original artifact hash. It never sends payment or creates a new admission. A free preview/status token cannot recover a paid result. Files are saved in a new private folder under evidence-live-receipts/exports/; the client prints its location. Keep the journal private. CSV text is protected against spreadsheet formulas and identifier rounding; original values remain in JSON. Exporting or recovering data does not establish settlement or refresh source records.

Integrate your own client

The HTTP workflow below is also available to compatible x402 clients. The preparation request needs no API key.

1. Prepare and inspect the offer — free

curl --fail-with-body --request POST \
  https://api.ai-analytics.org/paid/v1/evidence-jobs \
  --header 'Content-Type: application/json' \
  --data '{"identifier":"AAPL","expectedName":"Apple Inc."}'

For mine records, use the same preparation endpoint with {"product":"mine-records","mineId":"4801833"}. The returned preview identifies the product and exact mine. Company and mine artifacts use distinct schemas in the OpenAPI specification.

The response contains id, preview, quote, status_url and status_token. The quote supplies price_usd, admission_url and expires_at. Inspect coverage and identity before authorizing a purchase; use the returned offer and URL rather than constructing one from this example.

2. Buy the prepared admission — $0.02

Using your compatible client, send POST to the returned quote.admission_url. Follow the actual x402 challenge for its amount, asset, network and recipient. A plain unpaid request receives a payment challenge; it does not purchase the bundle.

The successful paid response contains the bundle and recovery: { url, token, expires_at }. Save the complete response and payment receipt in your client. Preparing a preview never makes a paid request; browser payment requires the separate reviewed authorization above.

3. Retrieve the original result — no new charge

curl --fail-with-body \
  'RECOVERY_URL_FROM_THE_PAID_RESPONSE' \
  --header 'Authorization: Bearer RECOVERY_TOKEN'

Use the returned recovery URL and token before their expiry. This is a GET for the original result, not another paid admission. Keep the recovery token private and out of shared URLs.

Payment authorization, settlement and result delivery are separate events. A 402 challenge or prepared job is not a settled purchase. Recovery depends on the capability returned with the paid result and its expiry.