{ "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:53:21.752288912Z", "lastOk": true, "lastStatus": 401, "lastMs": 584, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 597, "p95ms24h": 634, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "vendorStatus": { "page": "https://status.everee.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:31.139958321Z" }, "updatedAt": "2026-10-08T21:53:21.752288912Z" } }, "answer": "Gusto scores 63.3 (B) on agent readiness against Everee's 55.1 (C), and leads in 6 of 7 scored categories. Everee leads on reliability.", "b": { "slug": "gusto", "name": "Gusto", "vendor": "Gusto, Inc.", "vendorUrl": "https://gusto.com", "kind": "http-api", "category": "payroll", "summary": "Gusto Embedded Payroll is a REST API for running US payroll inside another product, covering company and worker onboarding, payroll calculation and submission, tax filing and contractor payments. Production access needs a partnership with Gusto. A demo environment is self-serve.", "url": "https://www.anchorterminal.com/tools/gusto", "markdownUrl": "https://www.anchorterminal.com/tools/gusto.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/gusto.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/gusto.json", "repo": "https://github.com/Gusto/gusto-typescript-client", "license": "Proprietary service under Gusto's API Policy and Developer Terms of Service. The API clients on GitHub are MIT, and the React SDK and the Gusto CLI are Apache-2.0", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@gusto/embedded-api" }, { "registry": "npm", "name": "@gusto/embedded-react-sdk" }, { "registry": "pypi", "name": "gusto-embedded" } ], "auth": "oauth", "authNotes": "Graded on the Embedded Payroll API, which needs a partnership. A developer signs up at dev.gusto.com, creates an organisation and an application, and gets a client ID and secret for the demo environment. POST /oauth/token with `grant_type` system_access returns a two-hour system token for partner-level calls, and creating a partner-managed company returns an access and refresh token pair for that company alone. Scopes are assigned by Gusto, and production keys follow commercial, security and implementation reviews. Access to an existing employer's Gusto account is separate. Partner apps use the App Integrations API with the OAuth 2.0 authorisation code grant after Production Pre-Approval and a security review. A customer's own company is reached through the Gusto CLI or the Gusto MCP server, which sign in by OAuth with dynamic client registration and PKCE.", "pricing": "paid", "pricingNotes": "No price could be read. gusto.com and embedded.gusto.com answered our reader with a bot check, and the developer docs carry no figures. The introduction says commercial conversations are required before production, and an invoices endpoint returns the active companies used to calculate a partner's invoice. The demo environment is open to any developer with a Developer Portal account, with generated demo companies and no contract (checked 2026-10-08).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the API reference or the llms.txt index (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 2, "npmWeekly": 24731, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.gusto.com/embedded-payroll/docs/introduction", "llmsTxt": "https://docs.gusto.com/llms.txt", "capabilities": [ "payroll.run", "payroll.employees", "payroll.embedded", "payroll.tax-filing", "payroll.contractors", "hr.onboarding", "hr.time-off" ], "tags": [ "hosted", "payroll", "oauth", "partner-approval", "sandbox", "llms-txt", "webhooks", "typescript", "python", "java", "csharp", "ruby", "mcp", "cli", "status-page" ], "lastRelease": "2026-10-01", "graded": true, "anchor": { "graded": true, "score": 63.3, "grade": "B", "agentReady": false, "rank": 314, "ranked": true, "rankOf": 722, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 82, "maintenance": 76, "payments": 15, "reliability": 58, "schema": 86, "security": 60, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "This listing covers the Embedded Payroll API. Every reference page carries an OpenAPI 3.1 definition, payroll is calculated as a preview before submission, and each API version gets 12 months of deprecation support. Production needs commercial and security approval, no price was readable, and the status page lists 11 incidents between 14 July and 5 October 2026, five marked major.", "bestFor": "A software platform that wants to run US payroll for its own customers and can pass Gusto's partner reviews.", "strengths": [ "Each of 317 reference pages serves an OpenAPI 3.1 definition as Markdown, and llms.txt indexes both documentation projects", "Payroll runs in steps (prepare, calculate, submit). Calculate returns a preview with `submission_blockers` before any money moves", "Each API version gets 12 months of phased support after deprecation, with dates published and `Deprecation`, `Sunset` and `Link` response headers", "Company access tokens work for one company only, expire after two hours and rotate the refresh token on use", "Rate limit of 200 requests a minute per application and user, with `Retry-After` and `X-RateLimit-*` headers on responses" ], "weaknesses": [ "Production keys need commercial, security and implementation reviews with Gusto's partnerships team, and the docs say not all use cases are supported", "The Embedded API status page lists 11 incidents between 14 July and 5 October 2026, five marked major, one titled a complete outage", "No price was readable. gusto.com and embedded.gusto.com answered our reader with a bot check, and the docs carry no figures", "Idempotency keys were found only on the People Batch endpoint. Other POST calls rely on the caller not repeating them", "The five API clients are labelled beta, and the README warns of breaking changes without notice" ], "agentNotes": [ "Develop against https://api.gusto-demo.com. Production at https://api.gusto.com needs keys Gusto issues after its reviews", "Send `X-Gusto-API-Version: 2026-06-15` on every call. Without it the application's minimum version applies", "Send the resource's current `version` with every PUT, and only the fields to change. A stale version returns 409", "Calculate and submit return 202. Poll GET on the payroll until `calculated_at` is set or the status is processed, and read `submission_blockers` first", "For a company already on Gusto, the Embedded API is the wrong route. Use the Gusto CLI or the MCP server at https://mcp.api.gusto.com, which draft payroll but can't submit it" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.3 } ], "editorialScores": { "ergonomics": 82, "maintenance": 76, "payments": 15, "reliability": 58, "schema": 86, "security": 60, "transparency": 44 }, "provenanceScore": 77 }, "connect": { "install": "npm add @gusto/embedded-api", "http": "curl --location --request POST 'https://api.gusto-demo.com/oauth/token' \\\n--header 'Content-Type: application/json' \\\n--data-raw '{\n \"client_id\": \"{{client_id}}\",\n \"client_secret\": \"{{client_secret}}\",\n \"grant_type\": \"system_access\"\n}'" }, "letme": { "capability": "https://letme.dev/payroll.run", "tool": "https://letme.dev/gusto" }, "area": "domain-data", "provenance": { "legalEntity": "Gusto, Inc.", "domain": "gusto.com", "domainRegistered": "1995-08-23", "endpointOnVendorDomain": true, "terms": "https://gusto.com/about/terms/developer-terms-of-service", "privacy": "", "statusPage": "https://gustoapi.statuspage.io", "changelog": "https://docs.gusto.com/embedded-payroll/changelog", "securityTxt": "unknown", "checked": "2026-10-08", "notes": [ "The NOTICE file in Gusto/gusto-cli reads Copyright 2026 Gusto, Inc.", "Production calls go to https://api.gusto.com. The demo environment is on a separate domain, api.gusto-demo.com.", "The terms URL is the one named in the OpenAPI definitions on the reference pages. gusto.com answered our reader with a bot check, so the terms, the privacy policy and /.well-known/security.txt weren't read.", "The API Policy published in the docs is dated 11 July 2022 and refers to Gusto's Privacy Policy without a readable link.", "RDAP for gusto.com gives a registration date of 1995-08-23.", "The docs embed https://gustoapi.statuspage.io as the API status page. status.gusto.com covers the Gusto product and also lists an API component." ], "score": 77 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/gusto.json", "live": { "slug": "gusto", "vendorStatus": { "page": "https://gustoapi.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:57:57.961908271Z" }, "versions": [ { "registry": "github", "name": "Gusto/gusto-typescript-client", "version": "gusto_embedded_v_2025_11_15/v0.3.2", "released": "2026-10-01", "seenAt": "2026-10-08T16:15:29.553541966Z" }, { "registry": "npm", "name": "@gusto/embedded-api", "version": "0.16.2", "seenAt": "2026-10-08T16:15:25.588820008Z" }, { "registry": "npm", "name": "@gusto/embedded-react-sdk", "version": "0.56.5", "seenAt": "2026-10-08T16:15:29.142122622Z" }, { "registry": "pypi", "name": "gusto-embedded", "version": "0.2.4", "released": "2025-04-16", "seenAt": "2026-10-08T16:15:29.349450484Z" } ], "githubStars": 2, "npmWeekly": 24731, "pypiWeekly": 104, "securityTxt": { "url": "https://gusto.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-10-08T15:38:35.992448629Z" }, "pages": [ { "url": "https://docs.gusto.com/embedded-payroll/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:18:50.184946965Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "fb0136facdba" }, { "url": "https://gusto.com/about/terms/developer-terms-of-service", "kind": "terms", "status": 403, "checkedAt": "2026-10-08T18:20:46.783185211Z", "changedAt": "0001-01-01T00:00:00Z" } ], "updatedAt": "2026-10-08T21:57:57.961908271Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Everee, Inc.", "b": "Gusto, Inc.", "name": "Vendor" }, { "a": "https://api.everee.com", "b": "no (local only)", "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 under Gusto's API Policy and Developer Terms of Service. The API clients on GitHub are MIT, and the React SDK and the Gusto CLI are Apache-2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-10-01", "name": "Last release" }, { "a": "2025-06-18", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2025-01-03", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "2 stars, 25k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Gusto scores 63.3 (B) on agent readiness against Everee's 55.1 (C), and leads in 6 of 7 scored categories. Everee leads on reliability.", "question": "Which is better for AI agents, Everee or Gusto?" }, { "answer": "Everee needs an API key. Gusto uses an OAuth sign-in.", "question": "Do Everee and Gusto need an API key?" }, { "answer": "Everee has a hosted endpoint at https://api.everee.com. No hosted endpoint is listed for Gusto.", "question": "Can an agent call Everee and Gusto without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 87 against 58" ], "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." }, { "aheadOn": [ "Schema \u0026 documentation, 86 against 67", "Agent ergonomics, 82 against 56", "Security \u0026 auth, 60 against 43", "Payments \u0026 pricing, 15 against 10", "Maintenance \u0026 community, 76 against 46", "Transparency \u0026 trust, 61 against 56" ], "also": null, "goodFor": "A software platform that wants to run US payroll for its own customers and can pass Gusto's partner reviews.", "slug": "gusto", "watchFor": "Production keys need commercial, security and implementation reviews with Gusto's partnerships team, and the docs say not all use cases are supported" } ], "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-gusto.json", "title": "Argyle vs Gusto", "url": "https://www.anchorterminal.com/compare/argyle-vs-gusto" }, { "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-gusto.json", "title": "Finch vs Gusto", "url": "https://www.anchorterminal.com/compare/finch-vs-gusto" }, { "json": "https://www.anchorterminal.com/compare/gusto-vs-paychex.json", "title": "Gusto vs Paychex", "url": "https://www.anchorterminal.com/compare/gusto-vs-paychex" }, { "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-gusto.json", "title": "Check vs Gusto", "url": "https://www.anchorterminal.com/compare/check-payroll-vs-gusto" }, { "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-gusto.json", "title": "Employment Hero Payroll vs Gusto", "url": "https://www.anchorterminal.com/compare/employment-hero-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-salsa.json", "title": "Gusto vs Salsa", "url": "https://www.anchorterminal.com/compare/gusto-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" } ], "scores": [ { "by": 29, "edge": "everee", "everee": 87, "gusto": 58, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 19, "edge": "gusto", "everee": 67, "gusto": 86, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 26, "edge": "gusto", "everee": 56, "gusto": 82, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 17, "edge": "gusto", "everee": 43, "gusto": 60, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "edge": "gusto", "everee": 10, "gusto": 15, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 30, "edge": "gusto", "everee": 46, "gusto": 76, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 5, "edge": "gusto", "everee": 56, "gusto": 61, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Gusto scores 63.3 (B) on agent readiness against Everee's 55.1 (C), and leads in 6 of 7 scored categories. Everee leads on reliability. 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.", "gusto": "This listing covers the Embedded Payroll API. Every reference page carries an OpenAPI 3.1 definition, payroll is calculated as a preview before submission, and each API version gets 12 months of deprecation support. Production needs commercial and security approval, no price was readable, and the status page lists 11 incidents between 14 July and 5 October 2026, five marked major." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/everee-vs-gusto", "json": "https://www.anchorterminal.com/compare/everee-vs-gusto.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/everee-vs-gusto.md", "slim": "https://www.anchorterminal.com/compare/everee-vs-gusto.min.md" }, "markdown": "Gusto scores 63.3 (B) on agent readiness against Everee's 55.1 (C), and leads in 6 of 7 scored categories. Everee leads on reliability. 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- Gusto: grade B, 63.3/100, rank #314 of 722. Markdown https://www.anchorterminal.com/tools/gusto.md · JSON https://www.anchorterminal.com/api/v1/tools/gusto.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 58\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### Gusto (B)\n\nGood for: A software platform that wants to run US payroll for its own customers and can pass Gusto's partner reviews.\n\nAhead on:\n- Schema \u0026 documentation, 86 against 67\n- Agent ergonomics, 82 against 56\n- Security \u0026 auth, 60 against 43\n- Payments \u0026 pricing, 15 against 10\n- Maintenance \u0026 community, 76 against 46\n- Transparency \u0026 trust, 61 against 56\n\nWatch for: Production keys need commercial, security and implementation reviews with Gusto's partnerships team, and the docs say not all use cases are supported\n\n\n## Score by category\n\n| Category | Weight | Everee | Gusto | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 87 | 58 | Everee +29 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 67 | 86 | Gusto +19 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 82 | Gusto +26 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 60 | Gusto +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 15 | Gusto +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 46 | 76 | Gusto +30 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 61 | Gusto +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **55.1 · C** | **63.3 · B** | |\n\n## Facts side by side\n\n| Fact | Everee | Gusto |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Everee, Inc. | Gusto, Inc. |\n| Hosted endpoint | `https://api.everee.com` | no (local only) |\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 under Gusto's API Policy and Developer Terms of Service. The API clients on GitHub are MIT, and the React SDK and the Gusto CLI are Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-10-01 |\n| Terms last updated | 2025-06-18 | couldn't be read |\n| Privacy policy last updated | 2025-01-03 | no document linked |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\n| Popularity | none | 2 stars, 25k 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**Gusto.** This listing covers the Embedded Payroll API. Every reference page carries an OpenAPI 3.1 definition, payroll is calculated as a preview before submission, and each API version gets 12 months of deprecation support. Production needs commercial and security approval, no price was readable, and the status page lists 11 incidents between 14 July and 5 October 2026, five marked major.\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### Gusto\n\n1. Develop against https://api.gusto-demo.com. Production at https://api.gusto.com needs keys Gusto issues after its reviews\n2. Send `X-Gusto-API-Version: 2026-06-15` on every call. Without it the application's minimum version applies\n3. Send the resource's current `version` with every PUT, and only the fields to change. A stale version returns 409\n4. Calculate and submit return 202. Poll GET on the payroll until `calculated_at` is set or the status is processed, and read `submission_blockers` first\n5. For a company already on Gusto, the Embedded API is the wrong route. Use the Gusto CLI or the MCP server at https://mcp.api.gusto.com, which draft payroll but can't submit it\n\n## Questions\n\n### Which is better for AI agents, Everee or Gusto?\n\nGusto scores 63.3 (B) on agent readiness against Everee's 55.1 (C), and leads in 6 of 7 scored categories. Everee leads on reliability.\n\n### Do Everee and Gusto need an API key?\n\nEveree needs an API key. Gusto uses an OAuth sign-in.\n\n### Can an agent call Everee and Gusto without installing anything?\n\nEveree has a hosted endpoint at https://api.everee.com. No hosted endpoint is listed for Gusto.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/everee-vs-gusto.json, and with the fewest tokens: https://www.anchorterminal.com/compare/everee-vs-gusto.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"everee\", \"b\": \"gusto\"}`. From a terminal: `anchor compare everee gusto`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/everee.json and https://www.anchorterminal.com/api/v1/tools/gusto.json\n\n## Other comparisons with Everee or Gusto\n\n- [Argyle vs Everee](https://www.anchorterminal.com/compare/argyle-vs-everee.md)\n- [Argyle vs Gusto](https://www.anchorterminal.com/compare/argyle-vs-gusto.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 Gusto](https://www.anchorterminal.com/compare/finch-vs-gusto.md)\n- [Gusto vs Paychex](https://www.anchorterminal.com/compare/gusto-vs-paychex.md)\n- [Check vs Everee](https://www.anchorterminal.com/compare/check-payroll-vs-everee.md)\n- [Check vs Gusto](https://www.anchorterminal.com/compare/check-payroll-vs-gusto.md)\n- [Employment Hero Payroll vs Everee](https://www.anchorterminal.com/compare/employment-hero-vs-everee.md)\n- [Employment Hero Payroll vs Gusto](https://www.anchorterminal.com/compare/employment-hero-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 Salsa](https://www.anchorterminal.com/compare/gusto-vs-salsa.md)\n- [Gusto vs Zeal](https://www.anchorterminal.com/compare/gusto-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 Gusto", "url": "" } ], "description": "Gusto scores 63.3 (B) on agent readiness against Everee's 55.1 (C), and leads in 6 of 7 scored categories. Everee leads on reliability. Both do payroll run. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Everee C 55.1", "Gusto B 63.3", "scores" ], "h1": "Everee vs Gusto", "image": "https://www.anchorterminal.com/assets/og/compare-everee-vs-gusto.png", "path": "/compare/everee-vs-gusto", "published": "2026-10-01", "section": "tools", "title": "Everee vs Gusto for AI agents, C 55.1 vs B 63.3 | Anchor Terminal", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/everee-vs-gusto" }, "tokens": { "markdown": 2150, "slim": 730 }, "version": 1 }