Authenticate to the Tax1099 API using your client credentials to obtain a Bearer token from the OAuth token endpoint
Create a payer record via POST to the payers endpoint supplying EIN, business name, and address fields for the filing entity
Submit each recipient record (contractor) via POST to the recipients endpoint with name, TIN, address, and the 'nonemployeeCompensation' amount for box 1 of the 1099-NEC
Trigger e-filing by calling the submit endpoint for the payer, specifying the tax year and form type '1099-NEC'; the API will validate the batch before transmitting to the IRS
Poll the filing status endpoint until the status transitions to 'Accepted' by the IRS, then download the recipient-copy PDFs for distribution to contractors
Known gotchas
The IRS FIRE system imposes a January 31 deadline for both recipient copies and IRS e-filing of 1099-NEC; late filing incurs per-form penalties that increase with delay duration
TIN mismatches between what you submit and IRS records generate B-Notices; always collect a signed W-9 before the first payment to ensure the TIN is correct
Corrections to already-accepted 1099-NEC forms require a separate corrected filing marked with the 'corrected' flag; you cannot simply resubmit the original record
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp