Abound
Abound was a US tax-compliance API company for platforms, marketplaces and fintechs serving the 1099 economy. Its v4 REST API covered the full information-return lifecycle: collecting Form W-9, W-8BEN and W-8BEN-E from payees, running real-time TIN verification against the IRS, then generating, filing, correcting, voiding and physically mailing Form 1099-NEC, 1099-MISC, 1099-K and 1099-INT to federal and state tax authorities. It also shipped drop-in UI components for payee onboarding, a 44-event webhook surface, and an official TypeScript SDK. Abound was acquired (announced November 2024) and the service has since been retired: the withabound.com DNS zone is fully de-delegated, the API and docs hosts no longer resolve, and the GitHub organization has been removed. This profile preserves the API surface, recovered from the first-party Fern API Definition shipped inside the official npm package.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Abound the way a machine reads it — 22 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Abound scores 36.4/100 (thin), with a separate agent-readiness read of 80/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Abound
Each block below is one kind of artifact we hold for Abound. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Abound 1099-INT API
The 1099-INT API from Abound — 6 operation(s) for 1099-int.
Abound 1099-K API
The 1099-K API from Abound — 6 operation(s) for 1099-k.
Abound 1099-MISC API
The 1099-MISC API from Abound — 6 operation(s) for 1099-misc.
Abound 1099-NEC API
The 1099-NEC API from Abound — 6 operation(s) for 1099-nec.
Abound Access Tokens API
The Access Tokens API from Abound — 1 operation(s) for access tokens.
Abound Electronic Delivery Consents API
The Electronic Delivery Consents API from Abound — 1 operation(s) for electronic delivery consents.
Abound Mailings API
The Mailings API from Abound — 2 operation(s) for mailings.
Abound Tax Treaties API
The Tax Treaties API from Abound — 1 operation(s) for tax treaties.
Abound TIN Verifications API
The TIN Verifications API from Abound — 2 operation(s) for tin verifications.
Abound Users API
The Users API from Abound — 2 operation(s) for users.
Abound W-8BEN API
The W-8BEN API from Abound — 2 operation(s) for w-8ben.
Abound W-8BEN-E API
The W-8BEN-E API from Abound — 2 operation(s) for w-8ben-e.
Abound W-9 API
The W-9 API from Abound — 2 operation(s) for w-9.
Scroll within the panel for all 13 ·
Arazzo Workflows 4
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOCollect a W-9 and verify the payee TIN
Create a user, collect their Form W-9, then run and read back a real-time TIN verification against the IRS.
ARAZZOCorrect or void a filed 1099-NEC
Fix a filed return - either file a correction or void it entirely. Both only work after the document is FILED.
ARAZZOCreate, file and mail a Form 1099-NEC
Run the full 1099-NEC lifecycle - create the document, file it with federal and state authorities, then mail the payee copy.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
abound-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Abound API v4 - Webhooks
The Abound webhook event surface: 44 HMAC-signed events covering Users, TIN Verifications, Mailings, Form 1099-INT/K/MISC/NEC and Forms W-9, W-8BEN and W-8BEN-E. Derived from th...
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Abound — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 11
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 11 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/abound · machine-readable index on apis.io