agentsapi-sec-filings

MCP server exposing SEC EDGAR filings as agent-callable tools — pay-per-call in USDC on Base via x402. No API key, no subscription: every call settles a micropayment on-chain and returns data immediately.

Tools

| Tool | Description | Price | |---|---|---| | sec_filings_today | Latest 10-K / 10-Q / 8-K filings across US markets, newest first (max 40) | $0.01 USDC / call | | sec_filings_8k | Real-time 8-K material events stream (M&A, executive changes, earnings, delisting, bankruptcy) | $0.005 USDC / call | | sec_filings_service_info | Free discovery: endpoints, prices, payment network, wallet | free |

Every paid response carries a receipt block (paid, payer, amount, transaction) so the caller can audit settlement.

Requirements

• Node.js >= 18
• An EVM wallet holding USDC on Base (mainnet, eip155:8453) plus a small amount of ETH for gas on the first transfer
• The private key is used locally to sign the x402 payment payload; it is never sent to the server

Install

npx agentsapi-sec-filings

Configuration

| Env var | Required | Default | Purpose | |---|---|---|---| | X402_PRIVATE_KEY | yes | — | EVM private key (0x...) used to sign payments | | X402_RPC_URL | no | https://mainnet.base.org | Base RPC endpoint | | AGENTSAPI_BASE | no | https://agentsapi.top | API base URL |

Claude Desktop / Claude Code

{
  "mcpServers": {
    "sec-filings": {
      "command": "npx",
      "args": ["-y", "agentsapi-sec-filings"],
      "env": {
        "X402_PRIVATE_KEY": "0x<your-base-wallet-key>"
      }
    }
  }
}

Cursor / Windsurf / any stdio MCP client

{
  "mcpServers": {
    "sec-filings": {
      "command": "npx",
      "args": ["-y", "agentsapi-sec-filings"],
      "env": { "X402_PRIVATE_KEY": "0x<your-base-wallet-key>" }
    }
  }
}

Example agent usage

"Any 8-K filings in the last few hours that look like M&A activity?"

The agent calls sec_filings_8k, the client answers the HTTP 402 challenge with a signed USDC transfer, and the filing list comes back with EDGAR links — $0.005 settled, no signup.

Payment flow

1. Tool call issues GET https://agentsapi.top/api/filings/8k
2. Server replies 402 Payment Required with x402 terms (USDC, Base, amount, payTo)
3. Client signs an EIP-3009 USDC authorization and retries with X-PAYMENT
4. Facilitator settles on-chain; server returns data + X-PAYMENT-RESPONSE receipt

Pricing rationale

• Data is refreshed every 10 minutes; each response contains up to 40 filings.
• No rate limits, no API keys — cost scales exactly with usage, which keeps agents free to call as needed.

License

MIT