{ "data": { "a": { "slug": "check-payroll", "name": "Check", "vendor": "Check Technologies, Inc.", "vendorUrl": "https://www.checkhq.com", "kind": "http-api", "category": "payroll", "summary": "Check is an embedded payroll API from Check Technologies in New York. Software platforms build US payroll on it for their own customers, with tax calculation, payment and filing handled by Check. Access is by partner agreement.", "url": "https://www.anchorterminal.com/tools/check-payroll", "markdownUrl": "https://www.anchorterminal.com/tools/check-payroll.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/check-payroll.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/check-payroll.json", "repo": "https://github.com/check-technologies/mcp-server-check", "license": "Proprietary service under Check's terms of service and partner agreement. The MCP server and CLI on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://api.checkhq.com", "packages": [], "auth": "mixed", "authNotes": "A partner API key sent as `Authorization: Bearer`, one for sandbox and one for production, issued by Check after a request through its sales contact. The key carries the whole partner account, with no per-key scopes found. Check says unused keys expire, last activity is shown and IP restrictions can be set through the account team. Integration partners get OAuth tokens (authorisation code grant, with refresh tokens) limited to one employer and one permission level, after a Check partner authorises them. The hosted MCP server accepts the API key or a Console OAuth login that runs with the Console user's permissions. This listing grades embedded-payroll partner access. Check has no route to an existing employer's payroll account outside a partner platform.", "pricing": "paid", "pricingNotes": "No public prices. checkhq.com/pricing returns 404 and the site's buttons open a sales contact form. A sandbox exists at sandbox.checkhq.com under a Sandbox User Agreement, but the documentation says to request an API key from Check, so an agent can't start without a person contacting sales. Production needs a partner agreement. The Usage API reports billable companies, employees and contractors each month, with no unit price published (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the documentation index, the API reference pages read or the website (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 18, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.checkhq.com", "llmsTxt": "https://docs.checkhq.com/llms.txt", "capabilities": [ "payroll.run", "payroll.employees", "payroll.embedded", "payroll.tax-filing", "payroll.contractors" ], "tags": [ "hosted", "embedded-payroll", "us-payroll", "api-key", "oauth", "mcp", "llms-txt", "sandbox", "webhooks", "sales-led", "partner-approval", "status-page", "bug-bounty", "soc2" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 67.5, "grade": "B", "agentReady": false, "rank": 208, "ranked": true, "rankOf": 722, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 72, "payments": 5, "reliability": 80, "schema": 78, "security": 74, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "`X-Idempotency-Key` is accepted on writes and stored for 24 hours, and a 429 carries `Retry-After` with `RateLimit-Limit` and `RateLimit-Remaining` on every authenticated response", "A payroll must have a succeeded preview before approval, and `preview_started_at` makes approval fail with 409 `preview_superseded` if the preview is stale", "Every response carries `X-Request-Log-Id`, and GET /logs returns request logs with SSNs, bank account numbers and the `Authorization` header redacted", "The MCP server starts with three meta-tools over 270 tools, with read-only mode, toolset filters and optional confirmation for destructive tools", "llms.txt indexes the documentation, and each page is served as Markdown with an OpenAPI 3.1 fragment per operation" ], "weaknesses": [ "No public price and no self-serve signup. The documentation says to request an API key through Check's sales contact", "An API key carries the whole partner account. No per-key scopes or read-only keys were found in the reviewed documentation", "No official SDK in a general programming language was found. The CLI and MCP server install from a git clone, not from PyPI", "No SLA is published. The terms of service make no representation about uptime unless agreed in writing", "No sub-processor list, hosting location or published DPA text was found, and the privacy policy states no retention periods" ], "agentNotes": [ "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", "Preview a payroll before approving it, then pass `preview_started_at` to POST /payrolls/{id}/approve so a stale preview fails with 409", "Send `X-Idempotency-Key` on every write. Keys expire after 24 hours, so list the resource before retrying later than that", "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", "Connect the MCP server with `?read_only=true` or `X-MCP-Readonly: true` unless writes are intended. In production, approving a payroll moves money" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.5 } ], "editorialScores": { "ergonomics": 83, "maintenance": 72, "payments": 5, "reliability": 80, "schema": 78, "security": 74, "transparency": 38 }, "provenanceScore": 86 }, "connect": { "http": "curl -X POST https://sandbox.checkhq.com/companies \\\n -H 'Content-Type: application/json' \\\n -H 'Authorization: Bearer \u003cAPI_KEY\u003e' \\\n -d '{\"address\": {\"line1\": \"20 W 34th St\", \"postal_code\": \"10001\", \"city\": \"New York\", \"state\": \"NY\"}, \"start_date\": \"2020-05-20\", \"trade_name\": \"Good Web Design\", \"legal_name\": \"Good Web Design, Inc.\"}'", "claudeCode": "claude mcp add --transport http check https://mcp.sandbox.checkhq.com/check/mcp \\\n --header \"Authorization: Bearer your-api-key-here\"", "config": { "mcpServers": { "check": { "type": "url", "url": "https://mcp.sandbox.checkhq.com/check/mcp" } } } }, "letme": { "capability": "https://letme.dev/payroll.run", "tool": "https://letme.dev/check-payroll" }, "area": "domain-data", "provenance": { "legalEntity": "Check Technologies, Inc.", "domain": "checkhq.com", "domainRegistered": "2006-10-28", "endpointOnVendorDomain": true, "terms": "https://www.checkhq.com/company/terms", "privacy": "https://www.checkhq.com/company/privacy", "statusPage": "https://status.checkhq.com", "changelog": "https://www.checkhq.com/resources/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The privacy policy (effective 18 April 2024) names Check Technologies, Inc., 228 Park Ave. S, PMB 14961, New York, NY 10003. The site footer also names Check Payments LLC (NMLS #2103307).", "The terms of service are dated 3 September 2021. Sandbox use is also governed by a Sandbox User Agreement at checkhq.com/company/sandbox-user-agreement.", "www.checkhq.com/.well-known/security.txt and checkhq.com/.well-known/security.txt return 404. The security page sends vulnerability reports to a bug bounty at federacy.com/check.", "The API answers at api.checkhq.com and sandbox.checkhq.com, and the hosted MCP server at mcp.checkhq.com and mcp.sandbox.checkhq.com.", "RDAP for checkhq.com gives a registration date of 2006-10-28 and Squarespace Domains II LLC as registrar." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/check-payroll.json", "live": { "slug": "check-payroll", "probe": { "target": "https://api.checkhq.com", "method": "get", "lastAt": "2026-10-08T21:53:18.965474157Z", "lastOk": true, "lastStatus": 200, "lastMs": 651, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 697, "p95ms24h": 1040, "samples24h": 71, "samples30d": 71, "days": [ { "date": "2026-10-08", "probes": 71, "ok": 71 } ] }, "vendorStatus": { "page": "https://status.checkhq.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:57:44.769154042Z" }, "githubStars": 18, "securityTxt": { "url": "https://checkhq.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:31.878118114Z" }, "pages": [ { "url": "https://www.checkhq.com/resources/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:27:02.804039275Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ada7be68b809" }, { "url": "https://www.checkhq.com/company/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:26:58.734249468Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2d782586e2af" }, { "url": "https://www.checkhq.com/company/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:27:00.809006213Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c2d2a944fcea" } ], "updatedAt": "2026-10-08T21:57:44.769154042Z" } }, "answer": "Check scores 67.5 (B) on agent readiness against Everee's 55.1 (C), and leads in 5 of 7 scored categories. Everee leads on reliability and payments \u0026 pricing.", "b": { "slug": "everee", "name": "Everee", "vendor": "Everee, Inc.", "vendorUrl": "https://www.everee.com", "kind": "http-api", "category": "payroll", "summary": "Payroll and worker payments from Everee, Inc. for United States employers and software platforms. A REST API onboards W-2 and 1099 workers, takes timesheets and payable items, requests payouts and reads pay history, with embeddable worker screens and webhooks.", "url": "https://www.anchorterminal.com/tools/everee", "markdownUrl": "https://www.anchorterminal.com/tools/everee.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/everee.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/everee.json", "license": "Proprietary service under Everee's Terms and Conditions and Payroll \u0026 Payment Service Terms. No open-source client or SDK was found", "transports": [ "http" ], "remoteUrl": "https://api.everee.com", "packages": [], "auth": "api-key", "authNotes": "An administrator of an Everee company instance creates an API token in Settings, Integrations Hub, with no review step described. Getting an instance starts with a demo call to sales. The token goes in an HTTP Basic `authorization` header with the instance's ID in `x-everee-tenant-id`, and a token starting `sk_` is Base64-encoded first. A token reaches one instance (one EIN) and carries no scopes in the docs. Tokens can be rotated or deleted, after which calls return 401. Everee rejects requests made from browsers. Platforms hold one token per customer instance.", "pricing": "paid", "pricingNotes": "No plan price is published. The pricing page names three usage-based models (per payment, per active employee, and revenue share or wholesale for technology partners), each with a custom quote. The pricing calculator's default inputs are a base price of $10 per paid worker a month and $0.75 per payment. The page lists a free sandbox, which follows a sales contact, so an agent can't start without a person booking a call (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the API reference or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.everee.com", "llmsTxt": "https://developer.everee.com/llms.txt", "capabilities": [ "payroll.run", "payroll.embedded", "payroll.employees", "payroll.contractors", "payroll.tax-filing", "hr.onboarding" ], "tags": [ "hosted", "closed-source", "api-key", "openapi", "llms-txt", "webhooks", "sandbox", "sales-led", "us-only", "status-page", "soc2" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 55.1, "grade": "C", "agentReady": false, "rank": 519, "ranked": true, "rankOf": 722, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 46, "payments": 10, "reliability": 87, "schema": 67, "security": 43, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Every docs page has a Markdown copy listed in `llms.txt`, and each reference page carries an OpenAPI 3.0.1 fragment with request and response schemas (51 operations).", "Payable items need an `externalId` that the API rejects when repeated, and changes to paid timesheets need `correction-authorized=true`.", "Rate limits are published (200 operations per 5 seconds) with `RateLimit-Remaining`, `RateLimit-Reset`, `RateLimit-Limit` and `RateLimit-Policy` response headers and backoff guidance.", "status.everee.com shows 90 days of history for four components. The API component logged 730 seconds of downtime between 11 July and 8 October 2026.", "An API token is tied to one company instance (one EIN), and an administrator can create, rotate and delete tokens in the Integrations Hub." ], "weaknesses": [ "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.", "The Terms and Conditions forbid access through any agent or tool other than Everee's software or a web browser, and forbid monitoring availability or benchmarking.", "A company instance starts with a demo call. No self-serve signup, public sandbox host or plan price was found, only calculator defaults of $10 per paid worker and $0.75 per payment.", "No SDK, single OpenAPI file or API changelog was found, and `developer.everee.com/changelog` returns 404.", "Tokens carry no scopes or read-only form in the docs, and no audit log or webhook signature was found." ], "agentNotes": [ "Send two headers on every call, `authorization: basic \u003ctoken\u003e` and `x-everee-tenant-id`. Base64-encode a token that starts with `sk_` first.", "Derive each payable's `externalId` from stable data, never a timestamp or UUID, so a retried create is rejected instead of paying twice.", "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.", "Send hourly wages through the Timesheets API, not Payables, and assign `workLocationId` so tax is worked out for the right jurisdiction.", "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." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.1 } ], "editorialScores": { "ergonomics": 56, "maintenance": 46, "payments": 10, "reliability": 87, "schema": 67, "security": 43, "transparency": 39 }, "provenanceScore": 73 }, "connect": { "http": "curl 'https://api.everee.com/integration/v1/workers?page=0\u0026size=20' \\\n --header 'accept: application/json' \\\n --header 'authorization: basic YOUR_API_TOKEN' \\\n --header 'x-everee-tenant-id: YOUR_TENANT_ID'" }, "letme": { "capability": "https://letme.dev/payroll.run", "tool": "https://letme.dev/everee" }, "area": "domain-data", "provenance": { "legalEntity": "Everee, Inc.", "domain": "everee.com", "domainRegistered": "2010-02-10", "endpointOnVendorDomain": true, "terms": "https://www.everee.com/terms-and-conditions/", "privacy": "https://www.everee.com/privacy-policy-2/", "statusPage": "https://status.everee.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The privacy policy (last updated 3 January 2025) names Everee, Inc., a Delaware corporation, with an address at 1895 E Rodeo Walk Dr, Suite B200.", "The Terms and Conditions (last updated 18 June 2025) cover the payment processing platform, APIs and software, and are governed by Utah law. The Payroll \u0026 Payment Service Terms of the same date sit beside them at https://www.everee.com/payroll-service-terms/.", "The API answers at https://api.everee.com and the docs at developer.everee.com (hosted on ReadMe).", "www.everee.com/.well-known/security.txt and developer.everee.com/.well-known/security.txt return 404.", "status.everee.com runs on Better Stack and was created on 18 August 2023.", "developer.everee.com/changelog returns 404, so the changelog field is empty.", "The Everee Visa Pay Card is issued by The Bancorp Bank, N.A., per the site footer.", "RDAP for everee.com gives a registration date of 2010-02-10 and Amazon Registrar, Inc. as registrar." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/everee.json", "live": { "slug": "everee", "probe": { "target": "https://api.everee.com", "method": "get", "lastAt": "2026-10-08T21:53:21.752288912Z", "lastOk": true, "lastStatus": 401, "lastMs": 584, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 597, "p95ms24h": 634, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "vendorStatus": { "page": "https://status.everee.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:31.139958321Z" }, "updatedAt": "2026-10-08T21:53:21.752288912Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Check Technologies, Inc.", "b": "Everee, Inc.", "name": "Vendor" }, { "a": "https://api.checkhq.com", "b": "https://api.everee.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Check's terms of service and partner agreement. The MCP server and CLI on GitHub are MIT", "b": "Proprietary service under Everee's Terms and Conditions and Payroll \u0026 Payment Service Terms. No open-source client or SDK was found", "name": "Licence" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-07", "b": "2026-10-06", "name": "Last release" }, { "a": "2021-09-03", "b": "2025-06-18", "name": "Terms last updated" }, { "a": "2024-04-18", "b": "2025-01-03", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "18 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Check scores 67.5 (B) on agent readiness against Everee's 55.1 (C), and leads in 5 of 7 scored categories. Everee leads on reliability and payments \u0026 pricing.", "question": "Which is better for AI agents, Check or Everee?" }, { "answer": "Check takes an API key or an OAuth sign-in. Everee needs an API key.", "question": "Do Check and Everee need an API key?" }, { "answer": "Yes. Check has a hosted endpoint at https://api.checkhq.com and Everee at https://api.everee.com.", "question": "Can an agent call Check and Everee without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 78 against 67", "Agent ergonomics, 83 against 56", "Security \u0026 auth, 74 against 43", "Maintenance \u0026 community, 72 against 46", "Transparency \u0026 trust, 62 against 56" ], "also": null, "goodFor": "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.", "slug": "check-payroll", "watchFor": "No public price and no self-serve signup. The documentation says to request an API key through Check's sales contact" }, { "aheadOn": [ "Reliability, 87 against 80", "Payments \u0026 pricing, 10 against 5" ], "also": null, "goodFor": "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.", "slug": "everee", "watchFor": "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." } ], "job": { "capability": "payroll.run", "name": "Payroll run" }, "others": [ { "json": "https://www.anchorterminal.com/compare/argyle-vs-check-payroll.json", "title": "Argyle vs Check", "url": "https://www.anchorterminal.com/compare/argyle-vs-check-payroll" }, { "json": "https://www.anchorterminal.com/compare/argyle-vs-everee.json", "title": "Argyle vs Everee", "url": "https://www.anchorterminal.com/compare/argyle-vs-everee" }, { "json": "https://www.anchorterminal.com/compare/check-payroll-vs-finch.json", "title": "Check vs Finch", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-finch" }, { "json": "https://www.anchorterminal.com/compare/check-payroll-vs-paychex.json", "title": "Check vs Paychex", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-paychex" }, { "json": "https://www.anchorterminal.com/compare/everee-vs-finch.json", "title": "Everee vs Finch", "url": "https://www.anchorterminal.com/compare/everee-vs-finch" }, { "json": "https://www.anchorterminal.com/compare/everee-vs-paychex.json", "title": "Everee vs Paychex", "url": "https://www.anchorterminal.com/compare/everee-vs-paychex" }, { "json": "https://www.anchorterminal.com/compare/check-payroll-vs-employment-hero.json", "title": "Check vs Employment Hero Payroll", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-employment-hero" }, { "json": "https://www.anchorterminal.com/compare/check-payroll-vs-gusto.json", "title": "Check vs Gusto", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-gusto" }, { "json": "https://www.anchorterminal.com/compare/check-payroll-vs-salsa.json", "title": "Check vs Salsa", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-salsa" }, { "json": "https://www.anchorterminal.com/compare/check-payroll-vs-zeal.json", "title": "Check vs Zeal", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-zeal" }, { "json": "https://www.anchorterminal.com/compare/employment-hero-vs-everee.json", "title": "Employment Hero Payroll vs Everee", "url": "https://www.anchorterminal.com/compare/employment-hero-vs-everee" }, { "json": "https://www.anchorterminal.com/compare/everee-vs-gusto.json", "title": "Everee vs Gusto", "url": "https://www.anchorterminal.com/compare/everee-vs-gusto" }, { "json": "https://www.anchorterminal.com/compare/everee-vs-salsa.json", "title": "Everee vs Salsa", "url": "https://www.anchorterminal.com/compare/everee-vs-salsa" }, { "json": "https://www.anchorterminal.com/compare/everee-vs-zeal.json", "title": "Everee vs Zeal", "url": "https://www.anchorterminal.com/compare/everee-vs-zeal" } ], "scores": [ { "by": 7, "check-payroll": 80, "edge": "everee", "everee": 87, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 11, "check-payroll": 78, "edge": "check-payroll", "everee": 67, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 27, "check-payroll": 83, "edge": "check-payroll", "everee": 56, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 31, "check-payroll": 74, "edge": "check-payroll", "everee": 43, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "check-payroll": 5, "edge": "everee", "everee": 10, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 26, "check-payroll": 72, "edge": "check-payroll", "everee": 46, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 6, "check-payroll": 62, "edge": "check-payroll", "everee": 56, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Check scores 67.5 (B) on agent readiness against Everee's 55.1 (C), and leads in 5 of 7 scored categories. Everee leads on reliability and payments \u0026 pricing. Both do payroll run.", "verdicts": { "check-payroll": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/check-payroll-vs-everee", "json": "https://www.anchorterminal.com/compare/check-payroll-vs-everee.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/check-payroll-vs-everee.md", "slim": "https://www.anchorterminal.com/compare/check-payroll-vs-everee.min.md" }, "markdown": "Check scores 67.5 (B) on agent readiness against Everee's 55.1 (C), and leads in 5 of 7 scored categories. Everee leads on reliability and payments \u0026 pricing. Both do payroll run.\n\n- Check: grade B, 67.5/100, rank #208 of 722. Markdown https://www.anchorterminal.com/tools/check-payroll.md · JSON https://www.anchorterminal.com/api/v1/tools/check-payroll.json\n- Everee: grade C, 55.1/100, rank #519 of 722. Markdown https://www.anchorterminal.com/tools/everee.md · JSON https://www.anchorterminal.com/api/v1/tools/everee.json\n\n## Which one, for what\n\n### Check (B)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 78 against 67\n- Agent ergonomics, 83 against 56\n- Security \u0026 auth, 74 against 43\n- Maintenance \u0026 community, 72 against 46\n- Transparency \u0026 trust, 62 against 56\n\nWatch for: No public price and no self-serve signup. The documentation says to request an API key through Check's sales contact\n\n### Everee (C)\n\nGood 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.\n\nAhead on:\n- Reliability, 87 against 80\n- Payments \u0026 pricing, 10 against 5\n\nWatch 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.\n\n\n## Score by category\n\n| Category | Weight | Check | Everee | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 87 | Everee +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 67 | Check +11 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 56 | Check +27 |\n| Security \u0026 auth | 14% (17.5 this run) | 74 | 43 | Check +31 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 5 | 10 | Everee +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 72 | 46 | Check +26 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 56 | Check +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **67.5 · B** | **55.1 · C** | |\n\n## Facts side by side\n\n| Fact | Check | Everee |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Check Technologies, Inc. | Everee, Inc. |\n| Hosted endpoint | `https://api.checkhq.com` | `https://api.everee.com` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Check's terms of service and partner agreement. The MCP server and CLI on GitHub are MIT | Proprietary service under Everee's Terms and Conditions and Payroll \u0026 Payment Service Terms. No open-source client or SDK was found |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-07 | 2026-10-06 |\n| Terms last updated | 2021-09-03 | 2025-06-18 |\n| Privacy policy last updated | 2024-04-18 | 2025-01-03 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 18 stars | none |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Check\n\n1. 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\n2. Preview a payroll before approving it, then pass `preview_started_at` to POST /payrolls/{id}/approve so a stale preview fails with 409\n3. Send `X-Idempotency-Key` on every write. Keys expire after 24 hours, so list the resource before retrying later than that\n4. 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\n5. Connect the MCP server with `?read_only=true` or `X-MCP-Readonly: true` unless writes are intended. In production, approving a payroll moves money\n\n### Everee\n\n1. Send two headers on every call, `authorization: basic \u003ctoken\u003e` and `x-everee-tenant-id`. Base64-encode a token that starts with `sk_` first.\n2. Derive each payable's `externalId` from stable data, never a timestamp or UUID, so a retried create is rejected instead of paying twice.\n3. 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.\n4. Send hourly wages through the Timesheets API, not Payables, and assign `workLocationId` so tax is worked out for the right jurisdiction.\n5. 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.\n\n## Questions\n\n### Which is better for AI agents, Check or Everee?\n\nCheck scores 67.5 (B) on agent readiness against Everee's 55.1 (C), and leads in 5 of 7 scored categories. Everee leads on reliability and payments \u0026 pricing.\n\n### Do Check and Everee need an API key?\n\nCheck takes an API key or an OAuth sign-in. Everee needs an API key.\n\n### Can an agent call Check and Everee without installing anything?\n\nYes. Check has a hosted endpoint at https://api.checkhq.com and Everee at https://api.everee.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/check-payroll-vs-everee.json, and with the fewest tokens: https://www.anchorterminal.com/compare/check-payroll-vs-everee.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"check-payroll\", \"b\": \"everee\"}`. From a terminal: `anchor compare check-payroll everee`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/check-payroll.json and https://www.anchorterminal.com/api/v1/tools/everee.json\n\n## Other comparisons with Check or Everee\n\n- [Argyle vs Check](https://www.anchorterminal.com/compare/argyle-vs-check-payroll.md)\n- [Argyle vs Everee](https://www.anchorterminal.com/compare/argyle-vs-everee.md)\n- [Check vs Finch](https://www.anchorterminal.com/compare/check-payroll-vs-finch.md)\n- [Check vs Paychex](https://www.anchorterminal.com/compare/check-payroll-vs-paychex.md)\n- [Everee vs Finch](https://www.anchorterminal.com/compare/everee-vs-finch.md)\n- [Everee vs Paychex](https://www.anchorterminal.com/compare/everee-vs-paychex.md)\n- [Check vs Employment Hero Payroll](https://www.anchorterminal.com/compare/check-payroll-vs-employment-hero.md)\n- [Check vs Gusto](https://www.anchorterminal.com/compare/check-payroll-vs-gusto.md)\n- [Check vs Salsa](https://www.anchorterminal.com/compare/check-payroll-vs-salsa.md)\n- [Check vs Zeal](https://www.anchorterminal.com/compare/check-payroll-vs-zeal.md)\n- [Employment Hero Payroll vs Everee](https://www.anchorterminal.com/compare/employment-hero-vs-everee.md)\n- [Everee vs Gusto](https://www.anchorterminal.com/compare/everee-vs-gusto.md)\n- [Everee vs Salsa](https://www.anchorterminal.com/compare/everee-vs-salsa.md)\n- [Everee vs Zeal](https://www.anchorterminal.com/compare/everee-vs-zeal.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Check vs Everee", "url": "" } ], "description": "Check scores 67.5 (B) on agent readiness against Everee's 55.1 (C), and leads in 5 of 7 scored categories. Everee leads on reliability and payments \u0026 pricing. Both do payroll run. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Check B 67.5", "Everee C 55.1", "scores" ], "h1": "Check vs Everee", "image": "https://www.anchorterminal.com/assets/og/compare-check-payroll-vs-everee.png", "path": "/compare/check-payroll-vs-everee", "published": "2026-10-01", "section": "tools", "title": "Check vs Everee for AI agents, B 67.5 vs C 55.1 | Anchor Terminal", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-everee" }, "tokens": { "markdown": 2200, "slim": 680 }, "version": 1 }