Head to head · Running payroll · October 2026 research run

Check vs Everee

Check scores 67.9 (B) on agent readiness against Everee's 51.7 (D), and leads in 5 of 7 scored categories. Everee leads on reliability and payments & pricing. Both do running payroll.

Best payroll APIs and embedded payroll for AI agents · All 55 payroll comparisons

Which one, for what

Check B

Best for A software platform that wants to sell US payroll inside its own product and can sign a partnership, with Check handling tax calculation, money movement and filings.

Ahead on

  • Schema & documentation, 78 against 67
  • Agent ergonomics, 83 against 53
  • Security & auth, 74 against 42
  • Maintenance & community, 72 against 6
  • Transparency & trust, 63 against 58

Watch for

No public price and no self-serve signup. The documentation says to request an API key through Check's sales contact

Everee D

Best for A staffing, delivery or vertical software platform, or a single employer, that pushes hours and flat payments for W-2 and 1099 workers and lets admins approve in Everee's portal.

Ahead on

  • Reliability, 87 against 80
  • Payments & pricing, 15 against 8

Watch for

No preview or approval endpoint was found. Payments are approved by a payroll admin in the Everee portal, or automatically if Everee sets that up.

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Check +66

Check 72

The product changelog's latest entry is 22 October 2026 (Employee Tax Statement Override API), and the MCP server repository's latest commit 31 October 2026 (30). Thirteen dated changelog entries since 3 August (three on 13 August, 20 August, 9 and 10 September, two on 1 October, three on 8 October, 15 and 22 October), read across four pages, and MCP repository commits on 37 days in the same period (20). Closed service with a dated changelog, a help centre and developer support. The MCP repository is public and merges numbered pull requests, but issue replies weren't readable (10 of 15). No official SDK in a general programming language was found, and the official MCP registry returned no entry for Check on 1 November. The CLI and MCP server are current (5 of 15). The repository runs lint and over 700 test functions in CI with a lock file. It has no tags and isn't published to PyPI (7 of 10). 30+20+10+5+7 = 72.

Everee 6

Docs per the 8 October check, not re-read on 4 November. Closed service with no dated changelog (developer.everee.com/changelog answered 404). The 8 October award of 30 rested on a reference guide's page stamp of 6 October 2026, and its 10 on 15 docs pages stamped between 27 July and 6 October. This run reads page dates that record no change as setting no recency (wrike, coinbase-mcp, agentweb), and they aren't releases or changelog entries. The last dated API change on record is the deprecated Timesheets overtime fields ceasing to work on 1 April 2026, 217 days ago (0). Fewer than three dated entries in the 90 days from 6 August (0). support@everee.com and a help centre our reader couldn't draw. No public changelog, issue tracker or community (4 of 15). No official SDK. The docs give embed sample code for five platforms (2 of 15). No public package or repository to judge (0 of 10). Total 6.

Security & auth Check +32

Check 74

A partner API key in the Authorization header, one per environment, carrying the whole partner account. Check says unused keys expire, last activity is shown and IP restrictions are available. Integration partners get OAuth tokens limited to one employer and permission level, and hosted MCP accepts a Console OAuth login bound to that user's role. No per-key scopes were found (22 of 30). The MCP server has read-only mode, toolset and tool filters and optional confirmation for destructive tools. The API requires a succeeded preview before approval and gates SSNs and account numbers behind the separately approved Sensitive Data API. No read-only API key was found (15 of 20). The MCP server's instructions tell the model to confirm before writes that affect payroll or money movement. No guidance on untrusted text in records was found (6 of 15). GET /logs with filters, X-Request-Log-Id, Console API logs for 14 days, last activity per key, and sensitive-data access logged (14 of 15). SOC 2 Type II, a bug bounty through Federacy and regular penetration tests per the security page. No security.txt on 1 November (17 of 20). 22+15+6+14+17 = 74.

Everee 42

Docs and site per the 8 October check, not re-read on 4 November. One API token per company instance, created, rotated and deleted by an administrator in the portal, with no scopes documented (20 of 30). Eight reference fragments declare an OAuth password flow with read and write scopes that the authentication guide doesn't mention, which we didn't count. Payments wait for a payroll admin's approval unless auto-approval is arranged, timesheet corrections are opt-in and browser requests are rejected. No read-only token (12 of 20). Responses carry text entered by workers and employers, with no guidance on untrusted content (3 of 15). A request_id on each response. No audit log or per-call log was found in the docs (2 of 15). The technology page says "SOC II Certified" with multi-factor authentication and encryption. No report, security.txt, disclosure policy or bounty found, and this run reads a bare SOC 2 claim with no report or disclosure route as 5 (5 of 20). Total 42.

Agent ergonomics Check +30

Check 83

limit sizes a page, and since version 2025-01-01 payrolls omit items unless include_items is set. No field selection. The MCP server exposes three meta-tools over 270 tools, with toolset filters and a read-only mode (20 of 25). Cursor pagination with next and previous, page sizes up to 100 or 500 on 19 endpoints, filters by company, workplace, status, ids and metadata (18 of 20). Typed error codes, field_path pointing at the invalid input, X-Request-Log-Id on every response and 409 preview_superseded on a stale approval (18 of 20). X-Idempotency-Key on writes with a stated 24-hour window and retry guidance, and the MCP server's source sets readOnlyHint, destructiveHint and idempotentHint on every tool (20). Few required fields on the operations read. No official SDK in a general programming language was found, only a Postman collection, a Python CLI and React Components (7 of 15). 20+18+18+20+7 = 83.

Everee 53

Docs per the 8 October check, not re-read on 4 November. size sets a page, default 20, and bulk endpoints take up to 1,000 earnings. No field selection (12 of 25). page and size on eight list endpoints with totalPages and totalElements, and filters by worker, payment, paid state, date and lifecycle status (15 of 20). A request_id header on each response and a table of 14 named Timesheets errors, with 400 declared on 20 operations and 401 on 8. The 8 October description of the error body (errorCode, errorMessage, path, timestamp) came from an unauthenticated call to the API, a probe this run doesn't use, and is struck, so the docs describe no general error envelope (8 of 20). externalId is required on payable items and rejects repeats, and corrections to paid timesheets need correction-authorized=true. No general idempotency header (13 of 20). No SDK in any language was found. Every call needs two headers, and embeddable screens cover onboarding and pay history (5 of 15). Total 53.

Schema & documentation Check +11

Check 78

Each reference page embeds an OpenAPI 3.1 fragment for its one operation, with typed parameters and request bodies. No single downloadable specification was found, and response bodies are given as examples, not schemas (15 of 25). llms.txt indexes 458 lines of guides and 280 reference links on 1 November, and each page is served as Markdown (10). Guides say when to use synchronous or asynchronous preview and how sandbox differs from production. Reference descriptions are one line on most operations read (14 of 20). Request bodies list required fields and formats such as dates. No enums were seen on the operations read, and query filters are plain strings (10 of 15). Curl examples in the quickstart and guides, an error envelope with input_errors and field_path, and a table of error types. Most reference pages document only the success response (14 of 15). Dated versions through Check-Version, an API upgrades page listing six versions since 2021-01-15, and a product changelog (15). 15+10+14+10+14+15 = 78.

Everee 67

Docs per the 8 October check, not re-read on 4 November. Each reference page embeds an OpenAPI 3.0.1 fragment for its operation with request and response schemas, 51 operations in all. No single downloadable file was found (17 of 25). llms.txt lists 79 pages, each with a Markdown copy (10). 40 of 51 operations carry a description, and the Timesheets and Payables guides say which API to use for which pay and when not to. Six operations have no summary and one is titled "Copy of" (14 of 20). 36 enums and 60 required lists, with 5 of 268 objects left bare and timestamps as epoch integers (11 of 15). 356 examples and a table of 14 Timesheets errors. 400 is declared on 20 operations, 401 on 8 and 429 on none, and the error envelope isn't described (9 of 15). Paths are versioned as v1 and v2. No changelog exists, and three migration guides stand in for one (6 of 15). Total 67.

Reliability Everee +7

Check 80

Read with the hosted lines and scored on the REST API under an embedded-payroll partnership. status.checkhq.com on Atlassian Statuspage lists four components (API, Console, Onboard, Payments) with incident history, read through its history.atom feed (20). From 3 August to 1 November 2026 the feed lists the Usage API unavailable from 1:00 to 2:40 pm ET on 9 September (one endpoint, billing reports), deposits delayed at The Bancorp Bank on 4 September with every payment sent on time by Check, and API request log search in Console delayed from 20 to 22 October with no logs lost, plus two announced database maintenances (6 September, 24 October). Each touched one endpoint or one surface, or a receiving bank, so minor only (20). The 6 June major on payroll preview and approval and the 31 July bank delays fall outside the 90 days. Limits with numbers, 10 to 80 requests a second by tier and 100 concurrent requests (15). 429 carries Retry-After, every response carries RateLimit-Limit and RateLimit-Remaining, and X-Idempotency-Key covers writes for 24 hours (15). No SLA is published, and the terms of service make no representation about uptime unless agreed in writing. The startups page claims 99.999 per cent historical uptime, which is a vendor claim (0). The REST API carries no beta label. The MCP server is labelled beta in its usage terms (10). 20+20+15+15+0+10 = 80.

Everee 87

Read with the hosted rubric, on the Integration API of a company instance. Everee's Terms and Conditions (18 June 2025, re-read on 4 November) bar crawling any page of the Site and access by any agent or robot other than a web browser, so no everee.com host, status page included, was re-read, and every reading below is per the 8 October check, not re-read on 4 November. status.everee.com on Better Stack lists API, Web App, Mobile App and Time Clock Terminal with 90 days of history (20). The two posted incidents in the 90 days to 8 October were three-minute outages of the Time Clock Terminal, none touching the API. The 8 October figure of 730 seconds of API downtime came from the page's index.json data file, which this run doesn't read, and is struck. 9 October to 4 November is unread, so the recorded award stands with no credit for that stretch (30). The limit is published as 200 operations per 5 seconds (15). The docs describe 429, exponential backoff with jitter and four RateLimit-* headers including the reset time. A repeated payable externalId is rejected. No Idempotency-Key or Retry-After is documented (12 of 15). The terms make no representation about uptime and no SLA was found (0). The API carries no beta label (10). Total 87.

Payments & pricing Everee +7

Check 8

Read with the hosted rubric. No x402, MPP or L402 (0). No public price. checkhq.com/pricing still returns 404 on 1 November and the site asks visitors to get in touch (0). A sandbox exists under a Sandbox User Agreement, but the key is requested from Check through its sales contact, so partial credit (5 of 20). A person must contact sales and sign a partner agreement before production (0). 0+0+5+0 = 5. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.

Everee 15

Pricing pages per the 8 October check, not re-read on 4 November. Read with the hosted rubric. No x402, MPP or L402 (0). Three pricing models are named, each behind a custom quote. The pricing calculator's defaults of $10 per paid worker a month and $0.75 per payment are the only figures, so partial credit (5 of 20). The pricing page lists a free sandbox, reached through a sales contact (5 of 20). A person books a call to get a company instance before any token exists (0). Total 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Score by category

CategoryWeightCheckEvereeEdge
Reliability16%8087Everee +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7867Check +11
Agent ergonomics13%8353Check +30
Security & auth14%7442Check +32
Payments & pricing10%815Everee +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%726Check +66
Transparency & trust7%6358Check +5
Negative events≤1500
TotalB 67.9/100D 51.7/100

Facts side by side

FactCheckEveree
KindHTTP APIHTTP API
VendorCheck Technologies, Inc.Everee, Inc.
Hosted endpointhttps://api.checkhq.comhttps://api.everee.com
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPaidPaid
x402nono
LicenceProprietary service under Check's terms of service and partner agreement. The MCP server and CLI on GitHub are MITProprietary service under Everee's Terms and Conditions and Payroll & Payment Service Terms. No open-source client or SDK was found
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-312026-10-06
Terms last updated2021-09-032025-06-18
Privacy policy last updated2024-04-182025-01-03
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity18 starsnone
Agent reviews2.5/5 (4)none

How the scores have moved

Verdicts

Check

Graded as embedded payroll through a partner API key, not access to an existing employer's payroll account. The API has idempotency keys on writes, a required preview before approval and queryable request logs. No price is public, a sandbox key comes through Check's sales team, and one API key carries the whole partner account.

Everee

Everee's API tokens are created in the admin portal of each company instance, and payments wait for a payroll admin's approval unless auto-approval is arranged. The API has no preview or approval endpoint, no single OpenAPI file, no SDK and no changelog, and a company instance starts with a sales call.

Before you call either

Check

  1. Use https://sandbox.checkhq.com with the sandbox key and https://api.checkhq.com with the production key. A key is not valid across environments
  2. Preview a payroll before approving it, then pass preview_started_at to POST /payrolls/{id}/approve so a stale preview fails with 409
  3. Send X-Idempotency-Key on every write. Keys expire after 24 hours, so list the resource before retrying later than that
  4. On 429 wait for Retry-After. The limit is 10 requests a second in sandbox and for partners paying fewer than 1,000 payees a month, with 100 concurrent requests
  5. Connect the MCP server with ?read_only=true or X-MCP-Readonly: true unless writes are intended. In production, approving a payroll moves money

Everee

  1. Send two headers on every call, authorization: basic <token> and x-everee-tenant-id. Base64-encode a token that starts with sk_ first.
  2. Derive each payable's externalId from stable data, never a timestamp or UUID, so a retried create is rejected instead of paying twice.
  3. For contractors, call POST /integration/v1/payables/payment-request after all payable items are sent and before admins approve. Without it contractors aren't paid.
  4. Send hourly wages through the Timesheets API, not Payables, and assign workLocationId so tax is worked out for the right jurisdiction.
  5. Don't expect the API to move money alone. Tell the user a payroll admin must approve in the portal unless auto-approval is enabled, and read Everee's terms on automated access first.

Questions

Which is better for AI agents, Check or Everee?

Check scores 67.9 (B) on agent readiness against Everee's 51.7 (D), and leads in 5 of 7 scored categories. Everee leads on reliability and payments & pricing.

Do Check and Everee need an API key?

Check takes an API key or an OAuth sign-in. Everee needs an API key.

Can an agent call Check and Everee without installing anything?

Yes. Check has a hosted endpoint at https://api.checkhq.com and Everee at https://api.everee.com.

Other comparisons with Check or Everee

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.