78trust / 100
Verify Filing
by realcite-filing in Security & trust
x402 APIPassing, checked 2 h ago
Verify an SEC filing: given a filer's CIK and a claimed accession number, does that filing actually exist, and does its form type/filing date match what's claimed? Checked against SEC EDGAR's submissions API. Catches a fabricated or misattributed filing citation, including a real-looking accession number paired with an invented form type or date.
POST https://goodsong.dev/verify/filing
Last 30 days
All checks passedSome failedAll failedNot checked
- Uptime
- 100%
- Response time
- 281 ms typical, 349 ms slowest 5%
- Last check
- 2 h ago
- Next check
- any minute now
How to call it
# See the payment challenge (nothing is charged)
curl -i -X POST "https://goodsong.dev/verify/filing" \
-H "content-type: application/json" \
-d '{"accession_number":"0000320193-23-000106","cik":"320193"}'import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client().register(
"eip155:8453",
new ExactEvmScheme(privateKeyToAccount(process.env.AGENT_KEY)),
);
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? Preflight it first for $0.005:
// GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fgoodsong.dev%2Fverify%2Ffiling
const res = await pay("https://goodsong.dev/verify/filing", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({"accession_number":"0000320193-23-000106","cik":"320193"}),
});
console.log(await res.json());Example input
{
"accession_number": "0000320193-23-000106",
"cik": "320193"
}Example output
{
"canonical": {
"accession_number": "0000320193-23-000106",
"cik": "0000320193",
"company": "Apple Inc.",
"filing_date": "2023-11-03",
"form": "10-K",
"report_date": "2023-09-30"
},
"checks": {
"date_match": true,
"exists": true,
"form_match": true
},
"cost": {
"amount": "0.005",
"currency": "USDC"
},
"evidence": [
{
"retrieved_at": "2026-08-30T12:00:00Z",
"source": "sec_edgar",
"url": "https://data.sec.gov/submissions/CIK0000320193.json"
}
],
"latency_ms": 240,
"verdict": "confirmed"
}Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 245 ms | $0.005 |
| 6 h ago | Passed | 402 | 291 ms | $0.005 |
| 9 h ago | Passed | 402 | 281 ms | $0.005 |
| 13 h ago | Passed | 402 | 229 ms | $0.005 |
| 17 h ago | Passed | 402 | 311 ms | $0.005 |
| 20 h ago | Passed | 402 | 257 ms | $0.005 |
| 24 h ago | Passed | 402 | 349 ms | $0.005 |
| 28 h ago | Passed | 402 | 289 ms | $0.005 |
| 31 h ago | Passed | 402 | 250 ms | $0.005 |
| 36 h ago | Passed | 402 | 364 ms | $0.005 |