{ "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": 600, "ranked": true, "rankOf": 842, "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-09T11:29:00.070924295Z", "lastOk": true, "lastStatus": 401, "lastMs": 599, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 594, "p95ms24h": 623, "samples24h": 172, "samples30d": 172, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 122, "ok": 122 } ] }, "vendorStatus": { "page": "https://status.everee.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:57:53.65806291Z" }, "updatedAt": "2026-10-09T11:29:00.070924295Z" } }, "answer": "Everee scores 55.1 (C) on agent readiness against Worklio's 38.6 (E), and leads in 4 of 7 scored categories. Worklio leads on security \u0026 auth and payments \u0026 pricing.", "b": { "slug": "worklio", "name": "Worklio", "vendor": "Worklio, Inc.", "vendorUrl": "https://www.worklio.com", "kind": "http-api", "category": "payroll", "summary": "Embedded US payroll from Worklio, Inc. for software platforms, PEOs and payroll bureaus. A partner's backend creates companies and workers, runs payroll in steps and reads tax forms through a REST API, with white-label screens as an alternative.", "url": "https://www.anchorterminal.com/tools/worklio", "markdownUrl": "https://www.anchorterminal.com/tools/worklio.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/worklio.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/worklio.json", "license": "Proprietary service. The public Terms of Use date from 2014 and the partner agreement isn't public. The front-end library sits in a private repository", "transports": [ "http" ], "remoteUrl": "https://api.worklio.com", "packages": [], "auth": "oauth", "authNotes": "Every call takes a bearer JWT from `POST https://api.worklio.com/connect/token`. In the sandbox a developer registers at apiweb.worklio.com/RegisterDeveloper and uses the password grant with the account's username and password, scope `api`, and a client secret the docs print and describe as shared by all sandbox users. Tokens last 24 hours. Browser apps use an OpenID Connect redirect flow through `@worklio/sdk`, which isn't published and is requested from support. Production credentials, single sign-on and allowed origins are set up by Worklio. A System user has full rights over every company it created. This is embedded-payroll partner access, with no route into an employer's payroll account elsewhere.", "pricing": "paid", "pricingNotes": "A partner's price is set in its agreement and isn't public. The partner pages publish retail list prices per person per month ($10 for Full-Service Payroll, $81 for all 19 modules) and call them illustrative, not a quote, with base, setup and per-use fees excluded. The sandbox is self-serve after developer registration, so an agent's owner can start without a contract. Whether registration asks for a card was not read, because apiweb.worklio.com disallows crawlers (checked 2026-10-09).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the reference pages read or the website (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://apidocs.worklio.com/docs/overview", "llmsTxt": "https://apidocs.worklio.com/llms.txt", "capabilities": [ "payroll.run", "payroll.embedded", "payroll.employees", "payroll.tax-filing", "payroll.contractors" ], "tags": [ "hosted", "closed-source", "oauth", "openapi", "llms-txt", "webhooks", "sandbox", "partner-access", "soc2", "iso27001" ], "lastRelease": "2026-06-30", "graded": true, "anchor": { "graded": true, "score": 38.6, "grade": "E", "agentReady": false, "rank": 812, "ranked": true, "rankOf": 842, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 44, "maintenance": 25, "payments": 25, "reliability": 25, "schema": 71, "security": 48, "transparency": 48 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -3, "negativeNotes": [ "30 June 2026. The changelog entry that announces the reworked Time-Off Requests API says the older `timeoffrequests` routes were replaced by hyphenated routes and tells integrators to update, in the same note and with no earlier notice found. Whether partners were told privately is unknown, so the smallest deduction applies (-3). https://apidocs.worklio.com/changelog/v1-api-updates" ], "verdict": "Worklio documents 853 REST operations with an OpenAPI fragment on every reference page, and a developer can register for the sandbox without a sales call. No rate limits or public SDK were found, the status page is password protected, and the payroll guide tells callers to treat an HTTP 500 as the signal to finalise.", "bestFor": "A software platform, PEO or payroll bureau that wants to sell US payroll under its own brand and can sign a partner agreement, with Worklio handling tax filing and money movement.", "strengths": [ "853 documented operations across 17 API groups, each reference page carrying an OpenAPI 3.0.4 fragment, plus llms.txt and a Markdown copy of every docs page", "Sandbox access is self-serve. A developer registers, uses a shared sandbox client secret printed in the docs and gets a bearer token", "A payroll run moves through steps with next, previous, discard, lock and finalise calls, and starting a scheduled run twice returns the same run", "Every operation states which user levels may call it (System, Admin, ClientAdmin, Employee, or anonymous with a link token)", "The security page claims SOC 2 Type 2, ISO 27001, ISO 27018 and ISO 9001, with third-party penetration testing" ], "weaknesses": [ "No rate limits, 429 handling or idempotency keys were found in the reviewed documentation", "status.worklio.com asks for a password, so no public incident history exists", "The Run Payroll guide says the `next` call answers HTTP 500 with an untranslated message when a run is ready to finalise", "No public SDK. `@worklio/sdk` and the component library sit in a private repository granted through support", "The public Terms of Use are dated 21 December 2014 and describe a small-business HR site. The partner agreement and production prices aren't public" ], "agentNotes": [ "Send `api-version: 2.0` on `/wep` calls. The reference marks the header as required", "Get a token from `POST https://api.worklio.com/connect/token` with the password grant and scope `api`. It lasts 24 hours, so fetch a new one daily", "Run payroll as start, `next` until it answers 500 with \"Next step operation is not allowed\", then `finalize`. Don't treat that 500 as a failure", "Don't retry bonus, off-cycle, void or termination payroll starts blindly. The reference says those calls are not idempotent", "Most `/wep` list endpoints return the whole result set. Paging, `filter` and `sort` work only under `/api/public`, and a `DataToken` expires after 60 seconds" ], "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": 38.6 } ], "editorialScores": { "ergonomics": 44, "maintenance": 25, "payments": 25, "reliability": 25, "schema": 71, "security": 48, "transparency": 28 }, "provenanceScore": 67 }, "connect": { "http": "curl -s -X POST \"https://api.worklio.com/connect/token\" \\\n -H \"accept: application/json\" \\\n -H \"content-type: application/x-www-form-urlencoded\" \\\n --data-urlencode \"grant_type=password\" \\\n --data-urlencode \"username=$WORKLIO_USERNAME\" \\\n --data-urlencode \"password=$WORKLIO_PASSWORD\" \\\n --data-urlencode \"scope=api\" \\\n --data-urlencode \"client_id=wep_resourceowner.public.api\" \\\n --data-urlencode \"client_secret=$WORKLIO_CLIENT_SECRET\"" }, "letme": { "capability": "https://letme.dev/payroll.run", "tool": "https://letme.dev/worklio" }, "area": "domain-data", "provenance": { "legalEntity": "Worklio, Inc.", "domain": "worklio.com", "domainRegistered": "2015-03-10", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://www.worklio.com/privacy", "statusPage": "", "changelog": "https://apidocs.worklio.com/changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The site footer reads \"© 2026 Worklio, Inc.\". The about page says Worklio LLC was established in 2017. No postal address was found on the pages read.", "No terms link is given. The only public terms are the Terms of Use at www.worklio.com/terms, last updated 21 December 2014, which describe an HR site for small businesses and predate the embedded API. The partner agreement that governs API use isn't public.", "www.worklio.com/privacy embeds a policy hosted at www.iubenda.com/privacy-policy/25719508. iubenda's robots.txt disallows that path, so the policy text was not read.", "status.worklio.com exists (an UptimeRobot page) and answers \"This status page is password protected\", so it is not recorded as a public status page.", "www.worklio.com/.well-known/security.txt returns 404.", "The changelog holds two entries, both dated 30 June 2026.", "RDAP for worklio.com gives a registration date of 2015-03-10." ], "score": 67 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/worklio.json", "live": { "slug": "worklio", "probe": { "target": "https://api.worklio.com", "method": "get", "lastAt": "2026-10-09T11:29:20.674813621Z", "lastOk": true, "lastStatus": 404, "lastMs": 464, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 472, "p95ms24h": 528, "samples24h": 41, "samples30d": 41, "days": [ { "date": "2026-10-09", "probes": 41, "ok": 41 } ] }, "updatedAt": "2026-10-09T11:29:20.674813621Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Everee, Inc.", "b": "Worklio, Inc.", "name": "Vendor" }, { "a": "https://api.everee.com", "b": "https://api.worklio.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth", "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 public Terms of Use date from 2014 and the partner agreement isn't public. The front-end library sits in a private repository", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-06-30", "name": "Last release" }, { "a": "2025-06-18", "b": "no document linked", "name": "Terms last updated" }, { "a": "2025-01-03", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "yes", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Everee scores 55.1 (C) on agent readiness against Worklio's 38.6 (E), and leads in 4 of 7 scored categories. Worklio leads on security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, Everee or Worklio?" }, { "answer": "Everee needs an API key. Worklio uses an OAuth sign-in.", "question": "Do Everee and Worklio need an API key?" }, { "answer": "Yes. Everee has a hosted endpoint at https://api.everee.com and Worklio at https://api.worklio.com.", "question": "Can an agent call Everee and Worklio without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 87 against 25", "Agent ergonomics, 56 against 44", "Maintenance \u0026 community, 46 against 25", "Transparency \u0026 trust, 56 against 48" ], "also": [ "No incidents deducted, where Worklio loses 3 points for them" ], "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": [ "Security \u0026 auth, 48 against 43", "Payments \u0026 pricing, 25 against 10" ], "also": null, "goodFor": "A software platform, PEO or payroll bureau that wants to sell US payroll under its own brand and can sign a partner agreement, with Worklio handling tax filing and money movement.", "slug": "worklio", "watchFor": "No rate limits, 429 handling or idempotency keys were found in the reviewed documentation" } ], "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-worklio.json", "title": "Argyle vs Worklio", "url": "https://www.anchorterminal.com/compare/argyle-vs-worklio" }, { "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-worklio.json", "title": "Finch vs Worklio", "url": "https://www.anchorterminal.com/compare/finch-vs-worklio" }, { "json": "https://www.anchorterminal.com/compare/paychex-vs-worklio.json", "title": "Paychex vs Worklio", "url": "https://www.anchorterminal.com/compare/paychex-vs-worklio" }, { "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-worklio.json", "title": "Check vs Worklio", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-worklio" }, { "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-worklio.json", "title": "Employment Hero Payroll vs Worklio", "url": "https://www.anchorterminal.com/compare/employment-hero-vs-worklio" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/gusto-vs-worklio.json", "title": "Gusto vs Worklio", "url": "https://www.anchorterminal.com/compare/gusto-vs-worklio" }, { "json": "https://www.anchorterminal.com/compare/salsa-vs-worklio.json", "title": "Salsa vs Worklio", "url": "https://www.anchorterminal.com/compare/salsa-vs-worklio" }, { "json": "https://www.anchorterminal.com/compare/worklio-vs-zeal.json", "title": "Worklio vs Zeal", "url": "https://www.anchorterminal.com/compare/worklio-vs-zeal" } ], "scores": [ { "by": 62, "edge": "everee", "everee": 87, "key": "reliability", "name": "Reliability", "weight": 16, "worklio": 25 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "edge": "worklio", "everee": 67, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "worklio": 71 }, { "by": 12, "edge": "everee", "everee": 56, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "worklio": 44 }, { "by": 5, "edge": "worklio", "everee": 43, "key": "security", "name": "Security \u0026 auth", "weight": 14, "worklio": 48 }, { "by": 15, "edge": "worklio", "everee": 10, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "worklio": 25 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 21, "edge": "everee", "everee": 46, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "worklio": 25 }, { "by": 8, "edge": "everee", "everee": 56, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "worklio": 48 } ], "summary": "Everee scores 55.1 (C) on agent readiness against Worklio's 38.6 (E), and leads in 4 of 7 scored categories. Worklio leads on security \u0026 auth and payments \u0026 pricing. 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.", "worklio": "Worklio documents 853 REST operations with an OpenAPI fragment on every reference page, and a developer can register for the sandbox without a sales call. No rate limits or public SDK were found, the status page is password protected, and the payroll guide tells callers to treat an HTTP 500 as the signal to finalise." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/everee-vs-worklio", "json": "https://www.anchorterminal.com/compare/everee-vs-worklio.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/everee-vs-worklio.md", "slim": "https://www.anchorterminal.com/compare/everee-vs-worklio.min.md" }, "markdown": "Everee scores 55.1 (C) on agent readiness against Worklio's 38.6 (E), and leads in 4 of 7 scored categories. Worklio leads on security \u0026 auth and payments \u0026 pricing. Both do payroll run.\n\n- Everee: grade C, 55.1/100, rank #600 of 842. Markdown https://www.anchorterminal.com/tools/everee.md · JSON https://www.anchorterminal.com/api/v1/tools/everee.json\n- Worklio: grade E, 38.6/100, rank #812 of 842. Markdown https://www.anchorterminal.com/tools/worklio.md · JSON https://www.anchorterminal.com/api/v1/tools/worklio.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 25\n- Agent ergonomics, 56 against 44\n- Maintenance \u0026 community, 46 against 25\n- Transparency \u0026 trust, 56 against 48\n\nAlso in its favour:\n- No incidents deducted, where Worklio loses 3 points for them\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### Worklio (E)\n\nGood for: A software platform, PEO or payroll bureau that wants to sell US payroll under its own brand and can sign a partner agreement, with Worklio handling tax filing and money movement.\n\nAhead on:\n- Security \u0026 auth, 48 against 43\n- Payments \u0026 pricing, 25 against 10\n\nWatch for: No rate limits, 429 handling or idempotency keys were found in the reviewed documentation\n\n\n## Score by category\n\n| Category | Weight | Everee | Worklio | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 87 | 25 | Everee +62 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 67 | 71 | Worklio +4 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 44 | Everee +12 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 48 | Worklio +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 25 | Worklio +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 46 | 25 | Everee +21 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 48 | Everee +8 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **55.1 · C** | **38.6 · E** | |\n\n## Facts side by side\n\n| Fact | Everee | Worklio |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Everee, Inc. | Worklio, Inc. |\n| Hosted endpoint | `https://api.everee.com` | `https://api.worklio.com` |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth |\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 public Terms of Use date from 2014 and the partner agreement isn't public. The front-end library sits in a private repository |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-06-30 |\n| Terms last updated | 2025-06-18 | no document linked |\n| Privacy policy last updated | 2025-01-03 | couldn't be read |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | yes | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | yes | |\n| Arbitration or class-action waiver | yes | |\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**Worklio.** Worklio documents 853 REST operations with an OpenAPI fragment on every reference page, and a developer can register for the sandbox without a sales call. No rate limits or public SDK were found, the status page is password protected, and the payroll guide tells callers to treat an HTTP 500 as the signal to finalise.\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### Worklio\n\n1. Send `api-version: 2.0` on `/wep` calls. The reference marks the header as required\n2. Get a token from `POST https://api.worklio.com/connect/token` with the password grant and scope `api`. It lasts 24 hours, so fetch a new one daily\n3. Run payroll as start, `next` until it answers 500 with \"Next step operation is not allowed\", then `finalize`. Don't treat that 500 as a failure\n4. Don't retry bonus, off-cycle, void or termination payroll starts blindly. The reference says those calls are not idempotent\n5. Most `/wep` list endpoints return the whole result set. Paging, `filter` and `sort` work only under `/api/public`, and a `DataToken` expires after 60 seconds\n\n## Questions\n\n### Which is better for AI agents, Everee or Worklio?\n\nEveree scores 55.1 (C) on agent readiness against Worklio's 38.6 (E), and leads in 4 of 7 scored categories. Worklio leads on security \u0026 auth and payments \u0026 pricing.\n\n### Do Everee and Worklio need an API key?\n\nEveree needs an API key. Worklio uses an OAuth sign-in.\n\n### Can an agent call Everee and Worklio without installing anything?\n\nYes. Everee has a hosted endpoint at https://api.everee.com and Worklio at https://api.worklio.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/everee-vs-worklio.json, and with the fewest tokens: https://www.anchorterminal.com/compare/everee-vs-worklio.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"everee\", \"b\": \"worklio\"}`. From a terminal: `anchor compare everee worklio`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/everee.json and https://www.anchorterminal.com/api/v1/tools/worklio.json\n\n## Other comparisons with Everee or Worklio\n\n- [Argyle vs Everee](https://www.anchorterminal.com/compare/argyle-vs-everee.md)\n- [Argyle vs Worklio](https://www.anchorterminal.com/compare/argyle-vs-worklio.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 Worklio](https://www.anchorterminal.com/compare/finch-vs-worklio.md)\n- [Paychex vs Worklio](https://www.anchorterminal.com/compare/paychex-vs-worklio.md)\n- [Check vs Everee](https://www.anchorterminal.com/compare/check-payroll-vs-everee.md)\n- [Check vs Worklio](https://www.anchorterminal.com/compare/check-payroll-vs-worklio.md)\n- [Employment Hero Payroll vs Everee](https://www.anchorterminal.com/compare/employment-hero-vs-everee.md)\n- [Employment Hero Payroll vs Worklio](https://www.anchorterminal.com/compare/employment-hero-vs-worklio.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- [Gusto vs Worklio](https://www.anchorterminal.com/compare/gusto-vs-worklio.md)\n- [Salsa vs Worklio](https://www.anchorterminal.com/compare/salsa-vs-worklio.md)\n- [Worklio vs Zeal](https://www.anchorterminal.com/compare/worklio-vs-zeal.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "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 Worklio", "url": "" } ], "description": "Everee scores 55.1 (C) on agent readiness against Worklio's 38.6 (E), and leads in 4 of 7 scored categories. Worklio leads on security \u0026 auth and payments \u0026 pricing. Both do payroll run. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Everee C 55.1", "Worklio E 38.6", "scores" ], "h1": "Everee vs Worklio", "image": "https://www.anchorterminal.com/assets/og/compare-everee-vs-worklio.png", "path": "/compare/everee-vs-worklio", "published": "2026-10-01", "section": "tools", "title": "Everee vs Worklio for AI agents, C 55.1 vs E 38.6 | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/everee-vs-worklio" }, "tokens": { "markdown": 2200, "slim": 680 }, "version": 1 }