{ "data": { "a": { "slug": "argyle", "name": "Argyle", "vendor": "Argyle Systems Inc.", "vendorUrl": "https://www.argyle.com", "kind": "http-api", "category": "payroll", "summary": "Argyle is a consumer-permissioned verification API run by Argyle Systems Inc. A worker connects a payroll account through Argyle Link, and applications read identity, employment, paystub and document records or order income and employment reports.", "url": "https://www.anchorterminal.com/tools/argyle", "markdownUrl": "https://www.anchorterminal.com/tools/argyle.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/argyle.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/argyle.json", "repo": "https://github.com/argyle-systems/argyle-link-react-native", "license": "Proprietary service under Argyle's Open Payroll Customer Terms. The React Native Link SDK on npm is Apache 2.0", "transports": [ "http" ], "remoteUrl": "https://api.argyle.com/v2", "packages": [ { "registry": "npm", "name": "@argyleio/argyle-plugin-react-native" } ], "auth": "api-key", "authNotes": "A person signs up for Console with a work email, Google or Microsoft account and creates an API key ID and secret for Sandbox or Production. Every request uses HTTP Basic auth with that pair. Access to a worker's payroll data then needs that worker to sign in to the payroll account through Argyle Link. Keys have no per-key scopes in the reviewed documentation, and a 403 means the key lacks a permission enabled for the account. The Customer Terms grant a licence for the platform to legal entities only, and Production fees are set in a Service Order.", "pricing": "paid", "pricingNotes": "No public prices. argyle.com/pricing lands on the home page, whose buttons are Sign in and Contact sales, and the Customer Terms put fees in a Service Order. A Sandbox with sample users comes with a Console sign-up, so an agent's owner can test without a contract. The sign-up page says Start your trial today. The docs list a `trial_connections_exhausted` error for a limit on free account connections in trial mode, with no number given (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the documentation index, the OpenAPI specification or the vendor's site (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 481, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.argyle.com", "llmsTxt": "https://docs.argyle.com/llms.txt", "openapi": "https://docs.argyle.com/openAPI/argyle-all.yaml", "capabilities": [ "payroll.employees", "payroll.contractors" ], "tags": [ "hosted", "payroll-data", "income-verification", "employment-verification", "api-key", "openapi", "llms-txt", "sandbox", "webhooks", "status-page", "sla", "security-txt", "sales-led" ], "lastRelease": "2026-10-01", "graded": true, "anchor": { "graded": true, "score": 63.7, "grade": "B", "agentReady": false, "rank": 297, "ranked": true, "rankOf": 722, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 58, "maintenance": 75, "payments": 15, "reliability": 81, "schema": 86, "security": 48, "transparency": 83 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Graded on the REST API. One OpenAPI file covers 91 operations, llms.txt indexes Markdown docs, and a Sandbox with sample users comes with a Console sign-up. Every payroll connection needs the worker to sign in through Link. No prices are published, no idempotency keys were found, and API keys carry no per-key scopes.", "bestFor": "A lender, tenant screener, benefits agency or background checker whose applicant can sign in to a payroll or gig account, and who needs paystubs, employment records or an income report.", "strengths": [ "One OpenAPI 3.0 file covers 91 operations and 119 schemas, and llms.txt indexes the documentation with every page served as Markdown", "Each payroll connection is made by the worker through Argyle Link, and the worker can remove it through Link or Argyle Passport", "A Sandbox at `https://api-sandbox.argyle.com/v2` has three sample users, simulated refreshes and its own API keys", "The rate limit is published as 50 requests a second, and Service Levels commit to 99 per cent monthly availability with credits", "The sub-processor list names 20 vendors with processing locations, and the DPA promises 30 days' notice before a new one is used", "Twelve dated changelog entries between 14 July and 1 October 2026, with a written definition of breaking changes" ], "weaknesses": [ "No price is published. The site has no pricing page, and fees are set in a Service Order agreed with sales", "No idempotency keys were found for `POST /users` or `POST /verifications`, and no `Retry-After` header is documented on 429 responses", "API keys are an ID and secret pair with no per-key scopes or read-only mode found in the reviewed documentation", "The OpenAPI file documents an error response on 2 of 91 operations, and general errors carry a `detail` string with no machine code", "No server-side SDK was found. The official SDKs are Link front ends for web, iOS, Android, React Native and Flutter", "The trust centre is drawn by script and could not be read, so no certification could be confirmed on the day" ], "agentNotes": [ "Send HTTP Basic auth with `api_key_id` as the username and `api_key_secret` as the password. Sandbox keys fail with 401 on Production and the reverse", "Create the user with `POST /v2/users` and an `external_id`, then look it up by `external_id` before retrying. No idempotency key was found", "Do not read data straight after an account connects. Wait for the account and data webhooks, or for the verification status, before fetching records", "Follow the full URL in `next` when paging. Do not build cursor values or fetch pages in parallel. `limit` defaults to 10 and stops at 200", "Stay under 50 requests a second. On 429, queue the request and retry later, not at once", "Treat `DELETE /v2/users/{id}` as permanent. It removes every resource tied to that user, with no confirmation step" ], "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.7 } ], "editorialScores": { "ergonomics": 58, "maintenance": 75, "payments": 15, "reliability": 81, "schema": 86, "security": 48, "transparency": 68 }, "provenanceScore": 97 }, "connect": { "http": "curl https://api-sandbox.argyle.com/v2/accounts \\\n -u api_key_id:api_key_secret" }, "letme": { "capability": "https://letme.dev/payroll.employees", "tool": "https://letme.dev/argyle" }, "area": "domain-data", "provenance": { "legalEntity": "Argyle Systems Inc.", "domain": "argyle.com", "domainRegistered": "1997-06-08", "endpointOnVendorDomain": true, "terms": "https://www.argyle.com/legal/open-payroll/customer-terms", "privacy": "https://www.argyle.com/legal/consumers/privacy-notice", "statusPage": "https://status.argyle.com", "changelog": "https://changelog.argyle.com", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Open Payroll Customer Terms (last updated 1 October 2026) name Argyle Systems Inc. and, with a Service Order, form the agreement for the API. Disputes go to the courts of New York, New York.", "The Privacy Notice (last updated 1 October 2026) covers the records a worker shares through the platform. Argyle describes itself there as a financial institution under the Gramm-Leach-Bliley Act. No separate privacy policy for business customers was found. Customer data is covered by the Data Protection Addendum at /legal/open-payroll/data-protection-addendum.", "The site also publishes Service Levels, a Support Policy, a sub-processor list and a Messaging Policy for Open Payroll, separate Open Banking Customer Terms, and Security Measures dated 6 June 2025.", "argyle.com/.well-known/security.txt gives security@argyle.com, a PGP key and an expiry of 7 May 2027.", "The API answers at api.argyle.com and api-sandbox.argyle.com. changelog.argyle.com redirects to docs.argyle.com/changelog.", "RDAP for argyle.com gives a registration date of 1997-06-08. The company's own llms.txt says it was founded in 2018." ], "score": 97 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/argyle.json", "live": { "slug": "argyle", "probe": { "target": "https://api.argyle.com/v2", "method": "get", "lastAt": "2026-10-08T21:12:04.288999451Z", "lastOk": true, "lastStatus": 404, "lastMs": 195, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 220, "p95ms24h": 315, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.argyle.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:05:51.399996556Z" }, "updatedAt": "2026-10-08T21:12:04.288999451Z" } }, "answer": "Argyle scores 63.7 (B) on agent readiness against Everee's 55.1 (C), and leads in 6 of 7 scored categories. Everee leads on reliability.", "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": "Argyle Systems Inc.", "b": "Everee, Inc.", "name": "Vendor" }, { "a": "https://api.argyle.com/v2", "b": "https://api.everee.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Argyle's Open Payroll Customer Terms. The React Native Link SDK on npm is Apache 2.0", "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": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-01", "b": "2026-10-06", "name": "Last release" }, { "a": "2026-10-01", "b": "2025-06-18", "name": "Terms last updated" }, { "a": "2026-10-01", "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": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "481 npm/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Argyle scores 63.7 (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, Argyle or Everee?" }, { "answer": "Both need an API key.", "question": "Do Argyle and Everee need an API key?" }, { "answer": "Yes. Argyle has a hosted endpoint at https://api.argyle.com/v2 and Everee at https://api.everee.com.", "question": "Can an agent call Argyle and Everee without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 86 against 67", "Security \u0026 auth, 48 against 43", "Payments \u0026 pricing, 15 against 10", "Maintenance \u0026 community, 75 against 46", "Transparency \u0026 trust, 83 against 56" ], "also": null, "goodFor": "A lender, tenant screener, benefits agency or background checker whose applicant can sign in to a payroll or gig account, and who needs paystubs, employment records or an income report.", "slug": "argyle", "watchFor": "No price is published. The site has no pricing page, and fees are set in a Service Order agreed with sales" }, { "aheadOn": [ "Reliability, 87 against 81" ], "also": null, "goodFor": "A staffing, delivery or vertical software platform, or a single employer, that pushes hours and flat payments for W-2 and 1099 workers and lets admins approve in Everee's portal.", "slug": "everee", "watchFor": "No preview or approval endpoint was found. Payments are approved by a payroll admin in the Everee portal, or automatically if Everee sets that up." } ], "job": { "capability": "payroll.employees", "name": "Payroll employees" }, "others": [ { "json": "https://www.anchorterminal.com/compare/argyle-vs-check-payroll.json", "title": "Argyle vs Check", "url": "https://www.anchorterminal.com/compare/argyle-vs-check-payroll" }, { "json": "https://www.anchorterminal.com/compare/argyle-vs-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-finch.json", "title": "Argyle vs Finch", "url": "https://www.anchorterminal.com/compare/argyle-vs-finch" }, { "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/argyle-vs-paychex.json", "title": "Argyle vs Paychex", "url": "https://www.anchorterminal.com/compare/argyle-vs-paychex" }, { "json": "https://www.anchorterminal.com/compare/argyle-vs-salsa.json", "title": "Argyle vs Salsa", "url": "https://www.anchorterminal.com/compare/argyle-vs-salsa" }, { "json": "https://www.anchorterminal.com/compare/argyle-vs-zeal.json", "title": "Argyle vs Zeal", "url": "https://www.anchorterminal.com/compare/argyle-vs-zeal" }, { "json": "https://www.anchorterminal.com/compare/everee-vs-finch.json", "title": "Everee vs Finch", "url": "https://www.anchorterminal.com/compare/everee-vs-finch" }, { "json": "https://www.anchorterminal.com/compare/everee-vs-paychex.json", "title": "Everee vs Paychex", "url": "https://www.anchorterminal.com/compare/everee-vs-paychex" }, { "json": "https://www.anchorterminal.com/compare/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-everee.json", "title": "Employment Hero Payroll vs Everee", "url": "https://www.anchorterminal.com/compare/employment-hero-vs-everee" }, { "json": "https://www.anchorterminal.com/compare/everee-vs-gusto.json", "title": "Everee vs Gusto", "url": "https://www.anchorterminal.com/compare/everee-vs-gusto" }, { "json": "https://www.anchorterminal.com/compare/everee-vs-salsa.json", "title": "Everee vs Salsa", "url": "https://www.anchorterminal.com/compare/everee-vs-salsa" }, { "json": "https://www.anchorterminal.com/compare/everee-vs-zeal.json", "title": "Everee vs Zeal", "url": "https://www.anchorterminal.com/compare/everee-vs-zeal" } ], "scores": [ { "argyle": 81, "by": 6, "edge": "everee", "everee": 87, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "argyle": 86, "by": 19, "edge": "argyle", "everee": 67, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "argyle": 58, "by": 2, "edge": "argyle", "everee": 56, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "argyle": 48, "by": 5, "edge": "argyle", "everee": 43, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "argyle": 15, "by": 5, "edge": "argyle", "everee": 10, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "argyle": 75, "by": 29, "edge": "argyle", "everee": 46, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "argyle": 83, "by": 27, "edge": "argyle", "everee": 56, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Argyle scores 63.7 (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 employees.", "verdicts": { "argyle": "Graded on the REST API. One OpenAPI file covers 91 operations, llms.txt indexes Markdown docs, and a Sandbox with sample users comes with a Console sign-up. Every payroll connection needs the worker to sign in through Link. No prices are published, no idempotency keys were found, and API keys carry no per-key scopes.", "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/argyle-vs-everee", "json": "https://www.anchorterminal.com/compare/argyle-vs-everee.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/argyle-vs-everee.md", "slim": "https://www.anchorterminal.com/compare/argyle-vs-everee.min.md" }, "markdown": "Argyle scores 63.7 (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 employees.\n\n- Argyle: grade B, 63.7/100, rank #297 of 722. Markdown https://www.anchorterminal.com/tools/argyle.md · JSON https://www.anchorterminal.com/api/v1/tools/argyle.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### Argyle (B)\n\nGood for: A lender, tenant screener, benefits agency or background checker whose applicant can sign in to a payroll or gig account, and who needs paystubs, employment records or an income report.\n\nAhead on:\n- Schema \u0026 documentation, 86 against 67\n- Security \u0026 auth, 48 against 43\n- Payments \u0026 pricing, 15 against 10\n- Maintenance \u0026 community, 75 against 46\n- Transparency \u0026 trust, 83 against 56\n\nWatch for: No price is published. The site has no pricing page, and fees are set in a Service Order agreed with sales\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 81\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 | Argyle | Everee | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 81 | 87 | Everee +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 67 | Argyle +19 |\n| Agent ergonomics | 13% (16.2 this run) | 58 | 56 | Argyle +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 43 | Argyle +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 10 | Argyle +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 46 | Argyle +29 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 56 | Argyle +27 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.7 · B** | **55.1 · C** | |\n\n## Facts side by side\n\n| Fact | Argyle | Everee |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Argyle Systems Inc. | Everee, Inc. |\n| Hosted endpoint | `https://api.argyle.com/v2` | `https://api.everee.com` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Argyle's Open Payroll Customer Terms. The React Native Link SDK on npm is Apache 2.0 | 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 | yes | yes |\n| Last release | 2026-10-01 | 2026-10-06 |\n| Terms last updated | 2026-10-01 | 2025-06-18 |\n| Privacy policy last updated | 2026-10-01 | 2025-01-03 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 481 npm/wk | none |\n\n## Verdicts\n\n**Argyle.** Graded on the REST API. One OpenAPI file covers 91 operations, llms.txt indexes Markdown docs, and a Sandbox with sample users comes with a Console sign-up. Every payroll connection needs the worker to sign in through Link. No prices are published, no idempotency keys were found, and API keys carry no per-key scopes.\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### Argyle\n\n1. Send HTTP Basic auth with `api_key_id` as the username and `api_key_secret` as the password. Sandbox keys fail with 401 on Production and the reverse\n2. Create the user with `POST /v2/users` and an `external_id`, then look it up by `external_id` before retrying. No idempotency key was found\n3. Do not read data straight after an account connects. Wait for the account and data webhooks, or for the verification status, before fetching records\n4. Follow the full URL in `next` when paging. Do not build cursor values or fetch pages in parallel. `limit` defaults to 10 and stops at 200\n5. Stay under 50 requests a second. On 429, queue the request and retry later, not at once\n6. Treat `DELETE /v2/users/{id}` as permanent. It removes every resource tied to that user, with no confirmation step\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, Argyle or Everee?\n\nArgyle scores 63.7 (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 Argyle and Everee need an API key?\n\nBoth need an API key.\n\n### Can an agent call Argyle and Everee without installing anything?\n\nYes. Argyle has a hosted endpoint at https://api.argyle.com/v2 and Everee at https://api.everee.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/argyle-vs-everee.json, and with the fewest tokens: https://www.anchorterminal.com/compare/argyle-vs-everee.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"argyle\", \"b\": \"everee\"}`. From a terminal: `anchor compare argyle everee`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/argyle.json and https://www.anchorterminal.com/api/v1/tools/everee.json\n\n## Other comparisons with Argyle or Everee\n\n- [Argyle vs Check](https://www.anchorterminal.com/compare/argyle-vs-check-payroll.md)\n- [Argyle vs Employment Hero Payroll](https://www.anchorterminal.com/compare/argyle-vs-employment-hero.md)\n- [Argyle vs Finch](https://www.anchorterminal.com/compare/argyle-vs-finch.md)\n- [Argyle vs Gusto](https://www.anchorterminal.com/compare/argyle-vs-gusto.md)\n- [Argyle vs Paychex](https://www.anchorterminal.com/compare/argyle-vs-paychex.md)\n- [Argyle vs Salsa](https://www.anchorterminal.com/compare/argyle-vs-salsa.md)\n- [Argyle vs Zeal](https://www.anchorterminal.com/compare/argyle-vs-zeal.md)\n- [Everee vs Finch](https://www.anchorterminal.com/compare/everee-vs-finch.md)\n- [Everee vs Paychex](https://www.anchorterminal.com/compare/everee-vs-paychex.md)\n- [Check vs Everee](https://www.anchorterminal.com/compare/check-payroll-vs-everee.md)\n- [Employment Hero Payroll vs Everee](https://www.anchorterminal.com/compare/employment-hero-vs-everee.md)\n- [Everee vs Gusto](https://www.anchorterminal.com/compare/everee-vs-gusto.md)\n- [Everee vs Salsa](https://www.anchorterminal.com/compare/everee-vs-salsa.md)\n- [Everee vs Zeal](https://www.anchorterminal.com/compare/everee-vs-zeal.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Argyle vs Everee", "url": "" } ], "description": "Argyle scores 63.7 (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 employees. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Argyle B 63.7", "Everee C 55.1", "scores" ], "h1": "Argyle vs Everee", "image": "https://www.anchorterminal.com/assets/og/compare-argyle-vs-everee.png", "path": "/compare/argyle-vs-everee", "published": "2026-10-01", "section": "tools", "title": "Argyle vs Everee for AI agents, B 63.7 vs C 55.1 | Anchor Terminal", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/argyle-vs-everee" }, "tokens": { "markdown": 2150, "slim": 630 }, "version": 1 }