{ "data": { "a": { "slug": "employment-hero", "name": "Employment Hero Payroll", "vendor": "Employment Hero Pty Ltd", "vendorUrl": "https://employmenthero.com", "kind": "http-api", "category": "payroll", "summary": "Employment Hero Payroll (formerly KeyPay) is cloud payroll for Australia, New Zealand, the United Kingdom, Singapore and Malaysia. Its REST API covers businesses, employees, timesheets, leave, pay runs and reports, with an API key or OAuth 2.0.", "url": "https://www.anchorterminal.com/tools/employment-hero", "markdownUrl": "https://www.anchorterminal.com/tools/employment-hero.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/employment-hero.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/employment-hero.json", "repo": "https://github.com/Thinkei/keypay-dotnet-v2", "license": "Proprietary service under Employment Hero's General Terms. The `KeyPayV2` .NET client is MIT", "transports": [ "http" ], "packages": [ { "registry": "nuget", "name": "KeyPayV2" } ], "auth": "mixed", "authNotes": "Graded on the Payroll API. A user with a payroll login generates an API key under My Account, with no partner review, and sends it as the HTTP Basic username with a blank password. The key acts with that user's access, and Change API Key invalidates the old one. OAuth 2.0 is the other route. A support request with the application's name, callback URL and logo returns a client ID and secret, and the authorisation code grant at `/oauth/authorise` and `/oauth/token` returns a 24-hour access token and a 28-day refresh token. The spec names `read` and `write` scopes, and the guide's sample token shows an empty scope.", "pricing": "paid", "pricingNotes": "No charge for API calls was found. Access comes with an Employment Hero Payroll subscription. The Australian pricing page lists the Payroll plan at $10 with conditions, a minimum of 10 users and billing by user count, with prices stated as AUD ex. GST in the page's disclaimers. Employment Unlimited, which includes Payroll, is priced through sales. No free tier, trial or sandbox for Payroll was found on the pages read, so an agent starts only where a paying account exists (checked 2026-10-08).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API guides, the five Swagger files or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 6, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://api.keypay.com.au/", "openapi": "https://api.keypay.com.au/swagger-au.json", "capabilities": [ "payroll.run", "payroll.employees", "payroll.embedded", "payroll.tax-filing", "payroll.contractors", "hr.time-off" ], "tags": [ "hosted", "payroll", "api-key", "oauth", "openapi", "webhooks", "dotnet", "white-label", "australia", "new-zealand", "uk", "singapore", "malaysia", "status-page" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 50.4, "grade": "D", "agentReady": false, "rank": 591, "ranked": true, "rankOf": 722, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 68, "payments": 10, "reliability": 65, "schema": 51, "security": 46, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Five public Swagger 2.0 files describe 660 to 821 operations per region, and any payroll user can generate an API key without a partner review. The key carries its user's whole access, no idempotency keys or API changelog were found, and the only official client is for .NET.", "bestFor": "An agent acting for an employer or bureau already on Employment Hero Payroll in Australia, New Zealand, the United Kingdom, Singapore or Malaysia, and white label partners who create businesses through the brand endpoints.", "strengths": [ "Public Swagger 2.0 file for each of five regions, 728 operations for Australia and 821 for the United Kingdom, downloadable without a login", "A payroll user generates an API key under My Account with no partner review, and Change API Key invalidates the old one", "OData `$filter`, `$orderby`, `$top` and `$skip` on most GET operations, with `$top` capped at 100", "Pay run endpoints cover create, recalculate, warnings, approval start, finalise and unlock, so a run can be checked before it is finalised", "The .NET client is regenerated from the API, with commits on 52 separate days between 10 July and 8 October 2026" ], "weaknesses": [ "An API key carries the whole access of the user who generated it. No per-key scopes were found", "No idempotency keys in the spec or guides, and 5 requests a second per key and IP address is the only documented limit", "No changelog, versioning policy or deprecation policy was found for the Payroll API", "Only 13 of 460 schema definitions in the Australian spec list required fields, and 711 of 728 operations document a 200 response and little else", "The developer forum's recent topics include spam, and several API questions from 2024 and 2025 show no replies" ], "agentNotes": [ "Send the API key as the Basic auth username with a blank password, for example `curl -u {api_key}: https://api.yourpayroll.com.au/api/v2/user`", "Pick the Swagger file for the business's region (`swagger-au.json`, `swagger-nz.json`, `swagger-uk.json`, `swagger-sg.json`, `swagger-my.json`). Paths and models differ by region", "Stay under 5 requests a second per key and IP address. A 429 answered our test with `retry-after: 1`", "Page lists with `$skip` and `$top` (100 at most). Filter property names are capitalised, unlike the camelCase JSON", "Read `GET /api/v2/business/{businessId}/payrun/{payRunId}/warnings` before `POST .../finalise`. Finalise can lodge with the tax office and publish pay slips in the same call" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.4 } ], "editorialScores": { "ergonomics": 53, "maintenance": 68, "payments": 10, "reliability": 65, "schema": 51, "security": 46, "transparency": 49 }, "provenanceScore": 71 }, "connect": { "install": "Install-Package KeyPayV2", "http": "curl -u {api_key}: https://api.yourpayroll.com.au/api/v2/user" }, "letme": { "capability": "https://letme.dev/payroll.run", "tool": "https://letme.dev/employment-hero" }, "area": "domain-data", "provenance": { "legalEntity": "Employment Hero Pty Ltd", "domain": "employmenthero.com", "domainRegistered": "2012-05-02", "endpointOnVendorDomain": false, "terms": "https://employmenthero.com/legals/terms-conditions/", "privacy": "https://employmenthero.com/legals/privacy-policy/", "statusPage": "https://status.employmenthero.com", "changelog": "", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The General Terms (effective 15 June 2026) name Employment Hero Pty Ltd and its affiliates, and define the EH Platform to include products reached through its APIs. They are the platform terms, and no separate API terms were found.", "The privacy policy is effective 3 June 2026 and points to a Data Processing Addendum effective 15 June 2026 at https://employmenthero.com/legals/privacy-policy/data-processing/.", "The API answers at api.yourpayroll.com.au and the documentation at api.keypay.com.au, both off employmenthero.com. RDAP for yourpayroll.com.au names the registrar only, so we could not confirm the registrant.", "https://employmenthero.com/.well-known/security.txt gives vuln@employmenthero.com, a policy link and an expiry of 31 December 2026.", "RDAP for employmenthero.com gives a registration date of 2012-05-02 and GoDaddy.com, LLC as registrar.", "No changelog for the Payroll API was found on the documentation site." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/employment-hero.json", "live": { "slug": "employment-hero", "vendorStatus": { "page": "https://status.employmenthero.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:03.50426119Z" }, "updatedAt": "2026-10-08T21:06:03.50426119Z" } }, "answer": "Everee scores 55.1 (C) on agent readiness against Employment Hero Payroll's 50.4 (D), and leads in 3 of 7 scored categories. Employment Hero Payroll leads on maintenance \u0026 community.", "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: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" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Employment Hero Pty Ltd", "b": "Everee, Inc.", "name": "Vendor" }, { "a": "no (local only)", "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 Employment Hero's General Terms. The `KeyPayV2` .NET client is 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": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-08", "b": "2026-10-06", "name": "Last release" }, { "a": "no date given", "b": "2025-06-18", "name": "Terms last updated" }, { "a": "no date given", "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": "6 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Everee scores 55.1 (C) on agent readiness against Employment Hero Payroll's 50.4 (D), and leads in 3 of 7 scored categories. Employment Hero Payroll leads on maintenance \u0026 community.", "question": "Which is better for AI agents, Employment Hero Payroll or Everee?" }, { "answer": "Employment Hero Payroll takes an API key or an OAuth sign-in. Everee needs an API key.", "question": "Do Employment Hero Payroll and Everee need an API key?" }, { "answer": "No hosted endpoint is listed for Employment Hero Payroll. Everee has a hosted endpoint at https://api.everee.com.", "question": "Can an agent call Employment Hero Payroll and Everee without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Maintenance \u0026 community, 68 against 46" ], "also": null, "goodFor": "An agent acting for an employer or bureau already on Employment Hero Payroll in Australia, New Zealand, the United Kingdom, Singapore or Malaysia, and white label partners who create businesses through the brand endpoints.", "slug": "employment-hero", "watchFor": "An API key carries the whole access of the user who generated it. No per-key scopes were found" }, { "aheadOn": [ "Reliability, 87 against 65", "Schema \u0026 documentation, 67 against 51" ], "also": [ "A hosted endpoint, with nothing to install" ], "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-employment-hero.json", "title": "Argyle vs Employment Hero Payroll", "url": "https://www.anchorterminal.com/compare/argyle-vs-employment-hero" }, { "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/employment-hero-vs-finch.json", "title": "Employment Hero Payroll vs Finch", "url": "https://www.anchorterminal.com/compare/employment-hero-vs-finch" }, { "json": "https://www.anchorterminal.com/compare/employment-hero-vs-paychex.json", "title": "Employment Hero Payroll vs Paychex", "url": "https://www.anchorterminal.com/compare/employment-hero-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-everee.json", "title": "Check vs Everee", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-everee" }, { "json": "https://www.anchorterminal.com/compare/employment-hero-vs-gusto.json", "title": "Employment Hero Payroll vs Gusto", "url": "https://www.anchorterminal.com/compare/employment-hero-vs-gusto" }, { "json": "https://www.anchorterminal.com/compare/employment-hero-vs-salsa.json", "title": "Employment Hero Payroll vs Salsa", "url": "https://www.anchorterminal.com/compare/employment-hero-vs-salsa" }, { "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/everee-vs-zeal.json", "title": "Everee vs Zeal", "url": "https://www.anchorterminal.com/compare/everee-vs-zeal" } ], "scores": [ { "by": 22, "edge": "everee", "employment-hero": 65, "everee": 87, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 16, "edge": "everee", "employment-hero": 51, "everee": 67, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 3, "edge": "everee", "employment-hero": 53, "everee": 56, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 3, "edge": "employment-hero", "employment-hero": 46, "everee": 43, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "edge": "", "employment-hero": 10, "everee": 10, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 22, "edge": "employment-hero", "employment-hero": 68, "everee": 46, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 4, "edge": "employment-hero", "employment-hero": 60, "everee": 56, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Everee scores 55.1 (C) on agent readiness against Employment Hero Payroll's 50.4 (D), and leads in 3 of 7 scored categories. Employment Hero Payroll leads on maintenance \u0026 community. Both do payroll run.", "verdicts": { "employment-hero": "Five public Swagger 2.0 files describe 660 to 821 operations per region, and any payroll user can generate an API key without a partner review. The key carries its user's whole access, no idempotency keys or API changelog were found, and the only official client is for .NET.", "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/employment-hero-vs-everee", "json": "https://www.anchorterminal.com/compare/employment-hero-vs-everee.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/employment-hero-vs-everee.md", "slim": "https://www.anchorterminal.com/compare/employment-hero-vs-everee.min.md" }, "markdown": "Everee scores 55.1 (C) on agent readiness against Employment Hero Payroll's 50.4 (D), and leads in 3 of 7 scored categories. Employment Hero Payroll leads on maintenance \u0026 community. Both do payroll run.\n\n- Employment Hero Payroll: grade D, 50.4/100, rank #591 of 722. Markdown https://www.anchorterminal.com/tools/employment-hero.md · JSON https://www.anchorterminal.com/api/v1/tools/employment-hero.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### Employment Hero Payroll (D)\n\nGood for: An agent acting for an employer or bureau already on Employment Hero Payroll in Australia, New Zealand, the United Kingdom, Singapore or Malaysia, and white label partners who create businesses through the brand endpoints.\n\nAhead on:\n- Maintenance \u0026 community, 68 against 46\n\nWatch for: An API key carries the whole access of the user who generated it. No per-key scopes were found\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 65\n- Schema \u0026 documentation, 67 against 51\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\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 | Employment Hero Payroll | Everee | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 87 | Everee +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 51 | 67 | Everee +16 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 56 | Everee +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 43 | Employment Hero Payroll +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 10 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 68 | 46 | Employment Hero Payroll +22 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 56 | Employment Hero Payroll +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.4 · D** | **55.1 · C** | |\n\n## Facts side by side\n\n| Fact | Employment Hero Payroll | Everee |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Employment Hero Pty Ltd | Everee, Inc. |\n| Hosted endpoint | no (local only) | `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 Employment Hero's General Terms. The `KeyPayV2` .NET client is 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 | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-08 | 2026-10-06 |\n| Terms last updated | no date given | 2025-06-18 |\n| Privacy policy last updated | no date given | 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 | 6 stars | none |\n\n## Verdicts\n\n**Employment Hero Payroll.** Five public Swagger 2.0 files describe 660 to 821 operations per region, and any payroll user can generate an API key without a partner review. The key carries its user's whole access, no idempotency keys or API changelog were found, and the only official client is for .NET.\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### Employment Hero Payroll\n\n1. Send the API key as the Basic auth username with a blank password, for example `curl -u {api_key}: https://api.yourpayroll.com.au/api/v2/user`\n2. Pick the Swagger file for the business's region (`swagger-au.json`, `swagger-nz.json`, `swagger-uk.json`, `swagger-sg.json`, `swagger-my.json`). Paths and models differ by region\n3. Stay under 5 requests a second per key and IP address. A 429 answered our test with `retry-after: 1`\n4. Page lists with `$skip` and `$top` (100 at most). Filter property names are capitalised, unlike the camelCase JSON\n5. Read `GET /api/v2/business/{businessId}/payrun/{payRunId}/warnings` before `POST .../finalise`. Finalise can lodge with the tax office and publish pay slips in the same call\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, Employment Hero Payroll or Everee?\n\nEveree scores 55.1 (C) on agent readiness against Employment Hero Payroll's 50.4 (D), and leads in 3 of 7 scored categories. Employment Hero Payroll leads on maintenance \u0026 community.\n\n### Do Employment Hero Payroll and Everee need an API key?\n\nEmployment Hero Payroll takes an API key or an OAuth sign-in. Everee needs an API key.\n\n### Can an agent call Employment Hero Payroll and Everee without installing anything?\n\nNo hosted endpoint is listed for Employment Hero Payroll. Everee has a hosted endpoint at https://api.everee.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/employment-hero-vs-everee.json, and with the fewest tokens: https://www.anchorterminal.com/compare/employment-hero-vs-everee.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"employment-hero\", \"b\": \"everee\"}`. From a terminal: `anchor compare employment-hero everee`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/employment-hero.json and https://www.anchorterminal.com/api/v1/tools/everee.json\n\n## Other comparisons with Employment Hero Payroll or Everee\n\n- [Argyle vs Employment Hero Payroll](https://www.anchorterminal.com/compare/argyle-vs-employment-hero.md)\n- [Argyle vs Everee](https://www.anchorterminal.com/compare/argyle-vs-everee.md)\n- [Employment Hero Payroll vs Finch](https://www.anchorterminal.com/compare/employment-hero-vs-finch.md)\n- [Employment Hero Payroll vs Paychex](https://www.anchorterminal.com/compare/employment-hero-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 Everee](https://www.anchorterminal.com/compare/check-payroll-vs-everee.md)\n- [Employment Hero Payroll vs Gusto](https://www.anchorterminal.com/compare/employment-hero-vs-gusto.md)\n- [Employment Hero Payroll vs Salsa](https://www.anchorterminal.com/compare/employment-hero-vs-salsa.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- [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": "Employment Hero Payroll vs Everee", "url": "" } ], "description": "Everee scores 55.1 (C) on agent readiness against Employment Hero Payroll's 50.4 (D), and leads in 3 of 7 scored categories. Employment Hero Payroll leads on maintenance \u0026 community. Both do payroll run. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Employment Hero Payroll D 50.4", "Everee C 55.1", "scores" ], "h1": "Employment Hero Payroll vs Everee", "image": "https://www.anchorterminal.com/assets/og/compare-employment-hero-vs-everee.png", "path": "/compare/employment-hero-vs-everee", "published": "2026-10-01", "section": "tools", "title": "Employment Hero Payroll vs Everee for AI agents, D 50.4 vs C 55.1", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/employment-hero-vs-everee" }, "tokens": { "markdown": 2250, "slim": 680 }, "version": 1 }