{ "data": { "a": { "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:12:09.940350512Z", "lastOk": true, "lastStatus": 401, "lastMs": 612, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 600, "p95ms24h": 634, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "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:12:09.940350512Z" } }, "answer": "Everee scores 55.1 (C) on agent readiness against Zeal's 45.4 (E), and leads in 4 of 7 scored categories. Zeal leads on agent ergonomics and maintenance \u0026 community.", "b": { "slug": "zeal", "name": "Zeal", "vendor": "Puzzl Group Inc.", "vendorUrl": "https://www.zeal.com", "kind": "http-api", "category": "payroll", "summary": "Zeal is an embedded payroll API for US staffing platforms, labour marketplaces and workforce software. Partners create employer companies, onboard W-2 employees and 1099 contractors, create pay cheques and contractor payments, preview payroll and pull reports.", "url": "https://www.anchorterminal.com/tools/zeal", "markdownUrl": "https://www.anchorterminal.com/tools/zeal.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zeal.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zeal.json", "repo": "https://github.com/zeal-corp/typescript-sdk", "license": "Proprietary service. The npm SDK declares MIT. The SDK repositories on GitHub carry no licence file", "transports": [ "http" ], "remoteUrl": "https://api.zeal.com", "packages": [ { "registry": "npm", "name": "@zeal-api/sdk" }, { "registry": "pypi", "name": "zeal-api-sdk" } ], "auth": "api-key", "authNotes": "API keys, issued only to Zeal partners. Zeal's team creates the partner account after a demo request, then the Partner Dashboard at app.zeal.com shows one Test API key, one Production API key and the `partnerID`. Every call sends `Authorization: Bearer {apiKey}`, and most also need a `companyID`. A key covers every employer company under the partner, has no scopes, and is rolled from the dashboard, which invalidates the old key at once. Production payroll is switched on by Zeal (error code 0 until then). The agent chat and MCP endpoints need a key that Zeal has Agent-enabled. This is embedded-payroll partner access. An employer has no separate API route into its own Zeal payroll account.", "pricing": "paid", "pricingNotes": "No public prices. www.zeal.com/pricing returns 404 and every call to action asks for a demo. A test environment that moves no money exists, but its key comes only after Zeal creates a partner account, so an agent cannot start without a sales contact. No free tier or self-serve trial was found (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms-full.txt, the OpenAPI specs or the marketing site (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 0, "npmWeekly": 8, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.zeal.com", "llmsTxt": "https://docs.zeal.com/llms.txt", "openapi": "https://docs.zeal.com/openapi/zeal-api.json", "capabilities": [ "payroll.run", "payroll.embedded", "payroll.employees", "payroll.contractors", "payroll.tax-filing", "hr.onboarding" ], "tags": [ "hosted", "api-key", "openapi", "llms-txt", "typescript", "python", "webhooks", "sandbox", "sales-led", "partner-only", "us-only", "soc2", "mcp" ], "lastRelease": "2026-07-31", "graded": true, "anchor": { "graded": true, "score": 45.4, "grade": "E", "agentReady": false, "rank": 658, "ranked": true, "rankOf": 722, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 61, "payments": 0, "reliability": 42, "schema": 68, "security": 34, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Graded on the partner REST API at api.zeal.com, which is the only access route. Three OpenAPI specs, llms.txt, a test environment that moves no money, a preview endpoint and a per-cheque approval flag are documented. Access starts with a demo request, prices are not published, each environment has one unscoped key, and no status page or working changelog was found.", "bestFor": "A US staffing platform, marketplace or workforce product that will sign a partnership and run payroll for many employers under its own brand, including daily and on-demand pay.", "strengths": [ "Public OpenAPI 3.1 specs with 177 operations, plus llms.txt, llms-full.txt and a Markdown copy of every docs page", "Test keys run payroll end to end with no money moved and no tax filings, in an environment separate from production", "Preview endpoints return the gross-to-net breakdown before processing, and `approval_required` holds a cheque until `approved` is set", "`x-idempotency-key` header honoured for 24 hours, and 116 numbered error codes with messages", "Fern-generated TypeScript and Python SDKs (0.2.1, July 2026) that retry 408, 429 and 5xx with backoff" ], "weaknesses": [ "No self-serve signup. Zeal's team creates the partner account after a demo request, and no price is published", "One test key and one production key per partner account, with no scopes and no read-only key", "No status page found, and the changelog linked from the home page and llms.txt returns 404", "The API has no version in the path or a header, and the main spec has 18 operations with no summary", "Webhooks carry the shared secret itself in `Puzzl-Signature`, not a signature of the payload", "No security.txt, disclosure policy, sub-processor list or DPA found on the public site" ], "agentNotes": [ "Use the Test API key until a person has approved live payroll. Error code 0 (403) means the account has no production access", "Send `companyID` on almost every call and `partnerID` on partner-level calls, in the body for POST and PATCH and the query for GET", "Create cheques with `approval_required: true`, run POST /preview/checks, then PATCH /employeeCheck with `approved: true`. Without the flag Zeal processes pending cheques automatically", "Send `x-idempotency-key` on every create so a retry within 24 hours doesn't pay twice", "Previews and reports are jobs. Keep the `job_id` and poll GET /preview or GET /reports, or wait for the Job Queue webhook", "Check dates must be bank days and submitted before 2 PM Pacific two bank days ahead, or the call fails with code 89" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.4 } ], "editorialScores": { "ergonomics": 63, "maintenance": 61, "payments": 0, "reliability": 42, "schema": 68, "security": 34, "transparency": 38 }, "provenanceScore": 64 }, "connect": { "install": "npm i -s @zeal-api/sdk", "http": "curl --request GET \\\n --url 'https://api.zeal.com/companies?partnerID=YOUR_PARTNER_ID' \\\n --header 'Accept: application/json' \\\n --header 'Authorization: Bearer YOUR_API_KEY'" }, "letme": { "capability": "https://letme.dev/payroll.run", "tool": "https://letme.dev/zeal" }, "area": "domain-data", "provenance": { "legalEntity": "Puzzl Group Inc.", "domain": "zeal.com", "domainRegistered": "1995-07-03", "endpointOnVendorDomain": true, "terms": "https://www.zeal.com/legal?tab=terms-of-service", "privacy": "https://www.zeal.com/legal?tab=privacy-policy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The legal page names Puzzl Group Inc., a Delaware corporation, 80 Langton Street, San Francisco, CA 94103. Its privacy notice was last updated on 16 January 2026.", "The API answers at https://api.zeal.com and docs at docs.zeal.com (hosted on Mintlify). The help centre at support.zeal.com runs on Pylon.", "www.zeal.com/.well-known/security.txt and docs.zeal.com/.well-known/security.txt return 404.", "No status page is linked from the site, the docs or the help centre. status.zeal.com did not complete a TLS handshake on 8 October 2026.", "The changelog URL the site advertises, https://docs.zeal.com/changelog, returns 404, so the field is left empty.", "The legal page says banking services come from Bangor Savings Bank, Member FDIC.", "RDAP for zeal.com gives a registration date of 1995-07-03 and GoDaddy.com, LLC as registrar." ], "score": 64 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zeal.json", "live": { "slug": "zeal", "probe": { "target": "https://api.zeal.com", "method": "get", "lastAt": "2026-10-08T21:12:26.455378082Z", "lastOk": true, "lastStatus": 200, "lastMs": 598, "authRequired": false, "uptime24h": 98.44, "uptime30d": 98.44, "p50ms24h": 604, "p95ms24h": 681, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-10-08", "probes": 64, "ok": 63 } ] }, "versions": [ { "registry": "npm", "name": "@zeal-api/sdk", "version": "0.2.1", "seenAt": "2026-10-08T16:35:37.1323379Z" }, { "registry": "pypi", "name": "zeal-api-sdk", "version": "0.2.1", "released": "2026-07-31", "seenAt": "2026-10-08T16:35:39.815769205Z" } ], "githubStars": 0, "npmWeekly": 8, "pypiWeekly": 4, "securityTxt": { "url": "https://zeal.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:30.40067532Z" }, "pages": [ { "url": "https://www.zeal.com/legal?tab=privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:44.751983613Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ca2c8021bf60" }, { "url": "https://www.zeal.com/legal?tab=terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:31:46.842036275Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ca2c8021bf60" } ], "updatedAt": "2026-10-08T21:12:26.455378082Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Everee, Inc.", "b": "Puzzl Group Inc.", "name": "Vendor" }, { "a": "https://api.everee.com", "b": "https://api.zeal.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Everee's Terms and Conditions and Payroll \u0026 Payment Service Terms. No open-source client or SDK was found", "b": "Proprietary service. The npm SDK declares MIT. The SDK repositories on GitHub carry no licence file", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-07-31", "name": "Last release" }, { "a": "2025-06-18", "b": "2026-01-16", "name": "Terms last updated" }, { "a": "2025-01-03", "b": "2026-01-16", "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": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "0 stars, 8 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Everee scores 55.1 (C) on agent readiness against Zeal's 45.4 (E), and leads in 4 of 7 scored categories. Zeal leads on agent ergonomics and maintenance \u0026 community.", "question": "Which is better for AI agents, Everee or Zeal?" }, { "answer": "Both need an API key.", "question": "Do Everee and Zeal need an API key?" }, { "answer": "Yes. Everee has a hosted endpoint at https://api.everee.com and Zeal at https://api.zeal.com.", "question": "Can an agent call Everee and Zeal without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 87 against 42", "Security \u0026 auth, 43 against 34", "Payments \u0026 pricing, 10 against 0", "Transparency \u0026 trust, 56 against 51" ], "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." }, { "aheadOn": [ "Agent ergonomics, 63 against 56", "Maintenance \u0026 community, 61 against 46" ], "also": null, "goodFor": "A US staffing platform, marketplace or workforce product that will sign a partnership and run payroll for many employers under its own brand, including daily and on-demand pay.", "slug": "zeal", "watchFor": "No self-serve signup. Zeal's team creates the partner account after a demo request, and no price is published" } ], "job": { "capability": "payroll.run", "name": "Payroll run" }, "others": [ { "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/argyle-vs-zeal.json", "title": "Argyle vs Zeal", "url": "https://www.anchorterminal.com/compare/argyle-vs-zeal" }, { "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/finch-vs-zeal.json", "title": "Finch vs Zeal", "url": "https://www.anchorterminal.com/compare/finch-vs-zeal" }, { "json": "https://www.anchorterminal.com/compare/paychex-vs-zeal.json", "title": "Paychex vs Zeal", "url": "https://www.anchorterminal.com/compare/paychex-vs-zeal" }, { "json": "https://www.anchorterminal.com/compare/check-payroll-vs-everee.json", "title": "Check vs Everee", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-everee" }, { "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/employment-hero-vs-zeal.json", "title": "Employment Hero Payroll vs Zeal", "url": "https://www.anchorterminal.com/compare/employment-hero-vs-zeal" }, { "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/gusto-vs-zeal.json", "title": "Gusto vs Zeal", "url": "https://www.anchorterminal.com/compare/gusto-vs-zeal" }, { "json": "https://www.anchorterminal.com/compare/salsa-vs-zeal.json", "title": "Salsa vs Zeal", "url": "https://www.anchorterminal.com/compare/salsa-vs-zeal" } ], "scores": [ { "by": 45, "edge": "everee", "everee": 87, "key": "reliability", "name": "Reliability", "weight": 16, "zeal": 42 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "edge": "zeal", "everee": 67, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "zeal": 68 }, { "by": 7, "edge": "zeal", "everee": 56, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "zeal": 63 }, { "by": 9, "edge": "everee", "everee": 43, "key": "security", "name": "Security \u0026 auth", "weight": 14, "zeal": 34 }, { "by": 10, "edge": "everee", "everee": 10, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "zeal": 0 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 15, "edge": "zeal", "everee": 46, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "zeal": 61 }, { "by": 5, "edge": "everee", "everee": 56, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "zeal": 51 } ], "summary": "Everee scores 55.1 (C) on agent readiness against Zeal's 45.4 (E), and leads in 4 of 7 scored categories. Zeal leads on agent ergonomics and maintenance \u0026 community. Both do payroll run.", "verdicts": { "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.", "zeal": "Graded on the partner REST API at api.zeal.com, which is the only access route. Three OpenAPI specs, llms.txt, a test environment that moves no money, a preview endpoint and a per-cheque approval flag are documented. Access starts with a demo request, prices are not published, each environment has one unscoped key, and no status page or working changelog was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/everee-vs-zeal", "json": "https://www.anchorterminal.com/compare/everee-vs-zeal.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/everee-vs-zeal.md", "slim": "https://www.anchorterminal.com/compare/everee-vs-zeal.min.md" }, "markdown": "Everee scores 55.1 (C) on agent readiness against Zeal's 45.4 (E), and leads in 4 of 7 scored categories. Zeal leads on agent ergonomics and maintenance \u0026 community. Both do payroll run.\n\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- Zeal: grade E, 45.4/100, rank #658 of 722. Markdown https://www.anchorterminal.com/tools/zeal.md · JSON https://www.anchorterminal.com/api/v1/tools/zeal.json\n\n## Which one, for what\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 42\n- Security \u0026 auth, 43 against 34\n- Payments \u0026 pricing, 10 against 0\n- Transparency \u0026 trust, 56 against 51\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### Zeal (E)\n\nGood for: A US staffing platform, marketplace or workforce product that will sign a partnership and run payroll for many employers under its own brand, including daily and on-demand pay.\n\nAhead on:\n- Agent ergonomics, 63 against 56\n- Maintenance \u0026 community, 61 against 46\n\nWatch for: No self-serve signup. Zeal's team creates the partner account after a demo request, and no price is published\n\n\n## Score by category\n\n| Category | Weight | Everee | Zeal | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 87 | 42 | Everee +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 67 | 68 | Zeal +1 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 63 | Zeal +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 34 | Everee +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 0 | Everee +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 46 | 61 | Zeal +15 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 51 | Everee +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **55.1 · C** | **45.4 · E** | |\n\n## Facts side by side\n\n| Fact | Everee | Zeal |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Everee, Inc. | Puzzl Group Inc. |\n| Hosted endpoint | `https://api.everee.com` | `https://api.zeal.com` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Everee's Terms and Conditions and Payroll \u0026 Payment Service Terms. No open-source client or SDK was found | Proprietary service. The npm SDK declares MIT. The SDK repositories on GitHub carry no licence file |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-07-31 |\n| Terms last updated | 2025-06-18 | 2026-01-16 |\n| Privacy policy last updated | 2025-01-03 | 2026-01-16 |\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 | yes | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | none | 0 stars, 8 npm/wk |\n\n## Verdicts\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**Zeal.** Graded on the partner REST API at api.zeal.com, which is the only access route. Three OpenAPI specs, llms.txt, a test environment that moves no money, a preview endpoint and a per-cheque approval flag are documented. Access starts with a demo request, prices are not published, each environment has one unscoped key, and no status page or working changelog was found.\n\n## Before you call either\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### Zeal\n\n1. Use the Test API key until a person has approved live payroll. Error code 0 (403) means the account has no production access\n2. Send `companyID` on almost every call and `partnerID` on partner-level calls, in the body for POST and PATCH and the query for GET\n3. Create cheques with `approval_required: true`, run POST /preview/checks, then PATCH /employeeCheck with `approved: true`. Without the flag Zeal processes pending cheques automatically\n4. Send `x-idempotency-key` on every create so a retry within 24 hours doesn't pay twice\n5. Previews and reports are jobs. Keep the `job_id` and poll GET /preview or GET /reports, or wait for the Job Queue webhook\n6. Check dates must be bank days and submitted before 2 PM Pacific two bank days ahead, or the call fails with code 89\n\n## Questions\n\n### Which is better for AI agents, Everee or Zeal?\n\nEveree scores 55.1 (C) on agent readiness against Zeal's 45.4 (E), and leads in 4 of 7 scored categories. Zeal leads on agent ergonomics and maintenance \u0026 community.\n\n### Do Everee and Zeal need an API key?\n\nBoth need an API key.\n\n### Can an agent call Everee and Zeal without installing anything?\n\nYes. Everee has a hosted endpoint at https://api.everee.com and Zeal at https://api.zeal.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/everee-vs-zeal.json, and with the fewest tokens: https://www.anchorterminal.com/compare/everee-vs-zeal.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"everee\", \"b\": \"zeal\"}`. From a terminal: `anchor compare everee zeal`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/everee.json and https://www.anchorterminal.com/api/v1/tools/zeal.json\n\n## Other comparisons with Everee or Zeal\n\n- [Argyle vs Everee](https://www.anchorterminal.com/compare/argyle-vs-everee.md)\n- [Argyle vs Zeal](https://www.anchorterminal.com/compare/argyle-vs-zeal.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- [Finch vs Zeal](https://www.anchorterminal.com/compare/finch-vs-zeal.md)\n- [Paychex vs Zeal](https://www.anchorterminal.com/compare/paychex-vs-zeal.md)\n- [Check vs Everee](https://www.anchorterminal.com/compare/check-payroll-vs-everee.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- [Employment Hero Payroll vs Zeal](https://www.anchorterminal.com/compare/employment-hero-vs-zeal.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- [Gusto vs Zeal](https://www.anchorterminal.com/compare/gusto-vs-zeal.md)\n- [Salsa vs Zeal](https://www.anchorterminal.com/compare/salsa-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": "Everee vs Zeal", "url": "" } ], "description": "Everee scores 55.1 (C) on agent readiness against Zeal's 45.4 (E), and leads in 4 of 7 scored categories. Zeal leads on agent ergonomics and maintenance \u0026 community. Both do payroll run. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Everee C 55.1", "Zeal E 45.4", "scores" ], "h1": "Everee vs Zeal", "image": "https://www.anchorterminal.com/assets/og/compare-everee-vs-zeal.png", "path": "/compare/everee-vs-zeal", "published": "2026-10-01", "section": "tools", "title": "Everee vs Zeal for AI agents, C 55.1 vs E 45.4 | Anchor Terminal", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/everee-vs-zeal" }, "tokens": { "markdown": 2150, "slim": 630 }, "version": 1 }