x402.ochinimus.app/api/sec-filings
SEC filings: the most recent EDGAR filings for a ticker, optionally one form type (10-K, 10-Q, 8-K, 4, S-1, 13F-HR), with filing date, report date, accession number, description, 8-K item codes and links to the document and the filing index. Use when you need to answer: What has this company filed with the SEC lately? Source: SEC EDGAR public filings.
Endpoint
https://x402.ochinimus.app/api/sec-filings
Verification
Checked 2 times without a pass yet. That is a fact about what our probes could establish, not a verdict on the endpoint: a route that validates a path parameter before it challenges, or serves its 402 only to POST, fails our check while working for a caller who knows the shape. The listing record shows what the probes found.
On-chain payments
Peak day 2026-10-08: 46 payments. Last indexed day 2026-10-15: 8. Our own index of USDC Transfer events on Base to this payTo, updated every 10 minutes; window is today plus the 30 prior UTC days. Base USDC only — a seller settling elsewhere reads as quiet here. These figures belong to the address, which 73 listings declare — they are not this route's alone, and must not be summed across listings. Methodology.
last 2 probes, oldest → newest · 100% pass · re-probed on its probe tier's interval (next_check_by on the record) from nohumans infrastructure — never self-reported
Payment protocols
x402 · MPP: This endpoint's 402 also offers payment over MPP (the "Payment" HTTP authentication scheme): tempo, as the endpoint names them. Read from our unpaid probes; mpp_offers lists each offer. Our paid verification and on-chain figures cover x402 on Base only.
Paid verification
Not yet paid-verified. Probe-based status above is liveness only.
Paid for this? Report the outcome
If you paid this endpoint on Base, tell the next buyer whether it delivered. The report is signed by the wallet that paid and the payment is checked on chain, so only real buyers can report; each transaction counts once and each payer has one voice. Nobody has reported on this listing yet. One call, with viem:
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(PAYER_KEY); // the wallet that paid
const txHash = "0x..."; // your payment to this endpoint, on Base
const ok = true; // did it deliver what it promised?
const message = "nohumans.directory report v1\nlisting_id: 464bdaee-6a4\ntx_hash: " + txHash.toLowerCase() + "\nok: " + ok;
const payer_signature = await account.signMessage({ message });
await fetch("https://api.nohumans.directory/v1/reports", {
method: "POST", headers: { "content-type": "application/json" },
body: JSON.stringify({ listing_id: "464bdaee-6a4", ok, tx_hash: txHash, payer_signature }),
});
Base payments only. More: /integrate.
Embed a badge
Own this listing? Paste a badge into your README or website. It links back to this page and updates automatically.
Status badge: the listing's current probe status (verified, failing or unverified).
[](https://nohumans.directory/l/464bdaee-6a4)
Machine interface
curl https://nohumans.directory/v1/listings/464bdaee-6a4
Own this service? Claim this listing to control its metadata — proof-of-control via your own endpoint, ~2 minutes. Works for submitted listings too, and recovers a lost token.
state of the network · methodology · stats · sellers · integrate · data · terms · privacy