Skip to main content
ClaudeWave
Edwardk91 avatar
Edwardk91

agentfilings-api

View on GitHub

Structured SEC/EDGAR filing data for AI agents - HTTP API and MCP server, pay-per-call via x402 on Base

MCP ServersOfficial Registry0 stars0 forksTypeScriptMITUpdated 1mo ago
ClaudeWave Trust Score
90/100
Verified
Passed
  • Open-source license (MIT)
  • Recently active
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 9/8/2026
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/Edwardk91/agentfilings-api
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "agentfilings-api": {
      "command": "node",
      "args": ["/path/to/agentfilings-api/dist/index.js"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/Edwardk91/agentfilings-api and follow its README for install instructions.
Use cases

MCP Servers overview

# AgentFilings

Structured US SEC/EDGAR filing data for AI agents — filings index, XBRL-derived
earnings, and Form 4 insider transactions as clean JSON, over both HTTP and MCP.

Two payment rails: **x402** (USDC on Base mainnet, no account required) for
autonomous agents, and a **flat Stripe subscription** for anyone who'd rather use a
card and an API key.

Live at [api.agentfilings.com](https://api.agentfilings.com) ·
[OpenAPI](https://api.agentfilings.com/openapi.json) ·
[llms.txt](https://api.agentfilings.com/llms.txt) ·
MCP at `https://api.agentfilings.com/mcp`

```bash
# Free. Tells you what data exists before you spend anything.
curl "https://api.agentfilings.com/probe?ticker=AAPL"
```

## What's actually interesting in here

Most of the work went into three things that are easy to get wrong with SEC data,
and one that's easy to get wrong with agent payments.

**Restatements.** `companyfacts` returns the same period once per filing that
reported it. When a company restates a figure, the superseded value is still in the
API. Each period here reconciles to its most recently filed value rather than the
first one encountered.

**Fiscal period provenance.** The `fy`/`fp` fields on a fact describe the *filing*,
not the period. A 10-Q showing last year's quarter as a comparative stamps that
older period with the newer filing's fiscal year. Each period here keeps the labels
from the filing that *originally* reported it. [`benchmark/`](./benchmark) is a
runnable measurement of how often those disagree.

**Entity identity.** SEC's ticker map can point at a post-reorganization shell that
holds the ticker and files no financial data. Resolution is CIK-authoritative, with
a guard that refuses to record coverage for an entity reporting no `us-gaap` facts.

**Payment replay.** Every x402 payment proof is bound to the specific resource it
paid for, so a proof issued for one endpoint or MCP tool cannot be replayed against
another. Settlement is idempotent, and EIP-712 domains are read per-network from the
USDC contracts rather than hardcoded.

## Honest coverage

`/probe` is free, and it will tell you **not** to pay:

```json
{
  "ticker_coverage": {
    "covered": true,
    "endpoints_with_data": ["/filings/latest", "/earnings/summary"],
    "empty_endpoints": ["/insiders"],
    "hint": "Partial coverage. /filings/latest and /earnings/summary will return data. /insiders would return an empty result, so do not pay for those."
  }
}
```

A company can be covered for filings and empty for earnings — foreign issuers
filing under IFRS, pre-revenue companies. Charging for a call that returns nothing
is the fastest way to lose an automated buyer permanently, so the service says so
before taking money.

## Layout

```
apps/api/          TypeScript / Hono — HTTP API + MCP server
  src/payments/    x402 v2: routes config, replay guard, idempotency, discovery
  src/billing/     Stripe rail: key issuance, subscription gate, checkout, webhook
  src/mcp/         MCP over streamable HTTP, paid tools
  src/repo/        Corpus access (Postgres in prod, local JSON in tests)
apps/ingest/       Python 3.12 — SEC ingestion, XBRL + Form 4 parsers
packages/shared/   Pricing table, x402 constants, response types
infra/migrations/  SQL schema
benchmark/         Standalone, runnable SEC XBRL correctness measurement
tests/             Cross-cutting, including the payment-security spec
```

`packages/shared/src/pricing.ts` is the single source of truth for the API surface.
The payment middleware, `/probe`, the MCP tool list and the OpenAPI document all
derive from it.

## Development

```bash
pnpm install
pnpm test        # vitest — api + shared
pnpm typecheck
pnpm lint
pnpm dev         # http://localhost:8080

curl localhost:8080/health
curl "localhost:8080/probe?ticker=AAPL"
```

Payments are gated off by default, so paid routes serve openly in development.
Ingestion requires `SEC_CONTACT_EMAIL` — the SEC requires a contact in the
User-Agent and blocks requests without one. See [`.env.example`](./.env.example)
and [`infra/DEPLOY.md`](./infra/DEPLOY.md).

## Principles

- **The free surface is honest.** `/health` and `/probe` are always free, and
  `/probe` never overstates coverage.
- **Never charge for what cannot be served.** An unimplemented endpoint is never
  payment-gated — the middleware would otherwise take payment and then 404.
- **Public domain only.** SEC EDGAR. No licensed datasets, no scraped transcripts.
- **Merchant only.** The service never holds, routes, or forwards third-party funds.

## Licence

MIT. Data is SEC EDGAR, public domain.
agent-toolsfinancial-datamcpmodel-context-protocolsec-edgarx402xbrl

What people ask about agentfilings-api

What is Edwardk91/agentfilings-api?

+

Edwardk91/agentfilings-api is mcp servers for the Claude AI ecosystem. Structured SEC/EDGAR filing data for AI agents - HTTP API and MCP server, pay-per-call via x402 on Base It has 0 GitHub stars and its last recorded update is dated 2026-08-03.

How do I install agentfilings-api?

+

You can install agentfilings-api by cloning the repository (https://github.com/Edwardk91/agentfilings-api) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is Edwardk91/agentfilings-api safe to use?

+

Our security agent has analyzed Edwardk91/agentfilings-api and assigned a Trust Score of 90/100 (tier: Verified). See the full breakdown of passed checks and flags on this page.

Who maintains Edwardk91/agentfilings-api?

+

Edwardk91/agentfilings-api is maintained by Edwardk91. The last recorded GitHub activity is dated 2026-08-03, with 0 open issues.

Are there alternatives to agentfilings-api?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy agentfilings-api to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: Edwardk91/agentfilings-api
[![Featured on ClaudeWave](https://claudewave.com/api/badge/edwardk91-agentfilings-api)](https://claudewave.com/repo/edwardk91-agentfilings-api)
<a href="https://claudewave.com/repo/edwardk91-agentfilings-api"><img src="https://claudewave.com/api/badge/edwardk91-agentfilings-api" alt="Featured on ClaudeWave: Edwardk91/agentfilings-api" width="320" height="64" /></a>

More MCP Servers

agentfilings-api alternatives