Skip to main content
This guide maps every AskEdgar dilution endpoint onto SEC API and walks through the auth, verification-model, and pricing changes you’ll see at cutover.

What changes when you switch

Per-field verification, not a boolean

Replace verified === true checks with the SEC API verification block (confidence, crossValidationsPassed, sourceSpanResolved).

Auth header swap

AskEdgar uses API-KEY: …; SEC API uses x-api-key: …. Same per-request shape, different header name.

Predictable subscription option

SEC API offers PAYG and flat subscriptions (55Personal,55 Personal, 239 Team). AskEdgar’s API is per-KB only.

Broader API surface

14 dilution endpoints plus 38 other endpoint families (filings, statements, factors, insiders, macro). One key, 39 families.

Hosted MCP and SDKs

106 MCP tools, including dilution workflows, and 4 SDKs (JS, Python, Go, Rust). AskEdgar also documents an MCP surface with API tools generated from OpenAPI, documentation tools, and Bearer API-key forwarding.

Route mapping

AskEdgar bundles warrants and convertibles into a single DilutionEntity. SEC API splits them into dedicated /v1/dilution/warrants and /v1/dilution/convertibles routes. Plan for a small shape change in your client when you cut over those reads.
  • /v1/dilution-data -> /v1/dilution/events
  • /v1/dilution-data?ticker={t}&id={id} -> /v1/dilution/events/{event_id}
  • /v1/dilution-rating (latest) -> /v1/dilution/score
  • /v1/dilution-rating (history) -> /v1/dilution/ratings
  • /v1/offerings -> /v1/dilution/events?form=S-1,S-3,424B5
  • /v1/registrations -> /v1/dilution/events?form=S-1,S-3
  • /v1/float-outstanding -> /v1/dilution/share-float-history?limit=1
  • /v1/historical-float-pro -> /v1/dilution/share-float-history
  • /v1/reverse-splits -> /v1/dilution/reverse-splits
  • /v1/nasdaq-compliance -> /v1/dilution/nasdaq-compliance
  • (no AskEdgar route) -> /v1/dilution/warrants
  • (no AskEdgar route) -> /v1/dilution/convertibles
  • (no AskEdgar route) -> /v1/dilution/rofr
  • (no AskEdgar route) -> /v1/dilution/lockups
  • (no AskEdgar route) -> /v1/dilution/cash-position
  • (no AskEdgar route) -> /v1/dilution/corporate-actions

Request translation examples

Dilution events for a ticker

Latest dilution score

Share-float history (full series)

Verification model migration

AskEdgar exposes a single boolean. SEC API exposes the components an agent can reason about:
Practical rewrite: replace verified === true checks with verification.confidence >= 0.9 && verification.sourceSpanResolved. Tighten or relax the threshold per workflow.

Pricing impact

AskEdgar’s API is strictly per-KB. SEC API offers PAYG (per-call) and flat subscriptions. The conversion lever depends on payload size and call volume: AskEdgar API costs assume the published /v1/dilution-data rate of $0.018/KB and a typical ~6 KB response. SEC API quotas reflect the published pricing. The 150 included calls are a one-time, non-renewing grant — see the billing FAQ.

Migration script template

Migration notes

  • Pin secapi-version in production clients before cutover.
  • Capture Request-Id during dual-run testing so request diagnostics stay comparable across the two providers.
  • AskEdgar’s verified: boolean collapses 6 dimensions into 1. Expect richer per-row metadata on SEC API; build your gating logic around the verification block, not a single flag.
  • AskEdgar’s API is metered per-KB; SEC API’s is per-call. For payload-heavy workloads the unit-cost story flips — re-benchmark before locking the pricing tier.
  • askedgar_url is preserved on every SEC API dilution row, so you can keep a back-link to the AskEdgar Copilot UI if your team wants to dual-source during cutover.
  1. issuer resolution and ticker mapping
  2. dilution events list (replaces /v1/dilution-data)
  3. dilution score and ratings (replaces /v1/dilution-rating)
  4. share-float history (replaces /v1/float-outstanding and /v1/historical-float-pro)
  5. nasdaq compliance and reverse splits (1:1 replacement)
  6. warrants and convertibles split (manual review of the bundled DilutionEntity shape)
  7. offerings and registrations (replaced by /v1/dilution/events with form filters)
  8. Use the documented filing and dilution-event routes for a bounded issuer list; SEC API does not provide a replacement for AskEdgar’s screener.
  9. Delivery webhooks/streams for public events such as monitor.match; dilution event fanout is reserved until the producer is public

Compare SEC API and AskEdgar

Side-by-side feature, schema, and pricing comparison.

Dilution endpoints

Open the 14 SEC API dilution routes with realistic examples.

Auth and pricing

Provision an org-scoped API key and review the PAYG ladder.