{ "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": 341, "ranked": true, "rankOf": 842, "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-09T10:14:08.201336437Z", "lastOk": true, "lastStatus": 404, "lastMs": 179, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 198, "p95ms24h": 267, "samples24h": 159, "samples30d": 159, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 109, "ok": 109 } ] }, "vendorStatus": { "page": "https://status.argyle.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T10:10:42.899267034Z" }, "updatedAt": "2026-10-09T10:14:08.201336437Z" } }, "answer": "Argyle scores 63.7 (B) on agent readiness against Worklio's 38.6 (E), and leads in 5 of 7 scored categories. Worklio leads on 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-09T10:14:32.874135866Z", "lastOk": true, "lastStatus": 404, "lastMs": 457, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 468, "p95ms24h": 504, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-09", "probes": 28, "ok": 28 } ] }, "updatedAt": "2026-10-09T10:14:32.874135866Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Argyle Systems Inc.", "b": "Worklio, Inc.", "name": "Vendor" }, { "a": "https://api.argyle.com/v2", "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 Argyle's Open Payroll Customer Terms. The React Native Link SDK on npm is Apache 2.0", "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-01", "b": "2026-06-30", "name": "Last release" }, { "a": "2026-10-01", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-10-01", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "", "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 Worklio's 38.6 (E), and leads in 5 of 7 scored categories. Worklio leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Argyle or Worklio?" }, { "answer": "Argyle needs an API key. Worklio uses an OAuth sign-in.", "question": "Do Argyle and Worklio need an API key?" }, { "answer": "Yes. Argyle has a hosted endpoint at https://api.argyle.com/v2 and Worklio at https://api.worklio.com.", "question": "Can an agent call Argyle and Worklio without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 81 against 25", "Schema \u0026 documentation, 86 against 71", "Agent ergonomics, 58 against 44", "Maintenance \u0026 community, 75 against 25", "Transparency \u0026 trust, 83 against 48" ], "also": [ "No incidents deducted, where Worklio loses 3 points for them" ], "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": [ "Payments \u0026 pricing, 25 against 15" ], "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.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-everee.json", "title": "Argyle vs Everee", "url": "https://www.anchorterminal.com/compare/argyle-vs-everee" }, { "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/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-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-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-worklio.json", "title": "Everee vs Worklio", "url": "https://www.anchorterminal.com/compare/everee-vs-worklio" }, { "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": [ { "argyle": 81, "by": 56, "edge": "argyle", "key": "reliability", "name": "Reliability", "weight": 16, "worklio": 25 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "argyle": 86, "by": 15, "edge": "argyle", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "worklio": 71 }, { "argyle": 58, "by": 14, "edge": "argyle", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "worklio": 44 }, { "argyle": 48, "by": 0, "edge": "", "key": "security", "name": "Security \u0026 auth", "weight": 14, "worklio": 48 }, { "argyle": 15, "by": 10, "edge": "worklio", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "worklio": 25 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "argyle": 75, "by": 50, "edge": "argyle", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "worklio": 25 }, { "argyle": 83, "by": 35, "edge": "argyle", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "worklio": 48 } ], "summary": "Argyle scores 63.7 (B) on agent readiness against Worklio's 38.6 (E), and leads in 5 of 7 scored categories. Worklio leads on payments \u0026 pricing. 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.", "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/argyle-vs-worklio", "json": "https://www.anchorterminal.com/compare/argyle-vs-worklio.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/argyle-vs-worklio.md", "slim": "https://www.anchorterminal.com/compare/argyle-vs-worklio.min.md" }, "markdown": "Argyle scores 63.7 (B) on agent readiness against Worklio's 38.6 (E), and leads in 5 of 7 scored categories. Worklio leads on payments \u0026 pricing. Both do payroll employees.\n\n- Argyle: grade B, 63.7/100, rank #341 of 842. Markdown https://www.anchorterminal.com/tools/argyle.md · JSON https://www.anchorterminal.com/api/v1/tools/argyle.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### 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- Reliability, 81 against 25\n- Schema \u0026 documentation, 86 against 71\n- Agent ergonomics, 58 against 44\n- Maintenance \u0026 community, 75 against 25\n- Transparency \u0026 trust, 83 against 48\n\nAlso in its favour:\n- No incidents deducted, where Worklio loses 3 points for them\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### 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- Payments \u0026 pricing, 25 against 15\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 | Argyle | Worklio | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 81 | 25 | Argyle +56 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 71 | Argyle +15 |\n| Agent ergonomics | 13% (16.2 this run) | 58 | 44 | Argyle +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 48 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 25 | Worklio +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 25 | Argyle +50 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 48 | Argyle +35 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **63.7 · B** | **38.6 · E** | |\n\n## Facts side by side\n\n| Fact | Argyle | Worklio |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Argyle Systems Inc. | Worklio, Inc. |\n| Hosted endpoint | `https://api.argyle.com/v2` | `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 Argyle's Open Payroll Customer Terms. The React Native Link SDK on npm is Apache 2.0 | 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-01 | 2026-06-30 |\n| Terms last updated | 2026-10-01 | no document linked |\n| Privacy policy last updated | 2026-10-01 | couldn't be read |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | 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**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### 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### 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, Argyle or Worklio?\n\nArgyle scores 63.7 (B) on agent readiness against Worklio's 38.6 (E), and leads in 5 of 7 scored categories. Worklio leads on payments \u0026 pricing.\n\n### Do Argyle and Worklio need an API key?\n\nArgyle needs an API key. Worklio uses an OAuth sign-in.\n\n### Can an agent call Argyle and Worklio without installing anything?\n\nYes. Argyle has a hosted endpoint at https://api.argyle.com/v2 and Worklio at https://api.worklio.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/argyle-vs-worklio.json, and with the fewest tokens: https://www.anchorterminal.com/compare/argyle-vs-worklio.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"argyle\", \"b\": \"worklio\"}`. From a terminal: `anchor compare argyle worklio`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/argyle.json and https://www.anchorterminal.com/api/v1/tools/worklio.json\n\n## Other comparisons with Argyle or Worklio\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 Everee](https://www.anchorterminal.com/compare/argyle-vs-everee.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- [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 Worklio](https://www.anchorterminal.com/compare/check-payroll-vs-worklio.md)\n- [Employment Hero Payroll vs Worklio](https://www.anchorterminal.com/compare/employment-hero-vs-worklio.md)\n- [Everee vs Worklio](https://www.anchorterminal.com/compare/everee-vs-worklio.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": "Argyle vs Worklio", "url": "" } ], "description": "Argyle scores 63.7 (B) on agent readiness against Worklio's 38.6 (E), and leads in 5 of 7 scored categories. Worklio leads on payments \u0026 pricing. Both do payroll employees. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Argyle B 63.7", "Worklio E 38.6", "scores" ], "h1": "Argyle vs Worklio", "image": "https://www.anchorterminal.com/assets/og/compare-argyle-vs-worklio.png", "path": "/compare/argyle-vs-worklio", "published": "2026-10-01", "section": "tools", "title": "Argyle vs Worklio for AI agents, B 63.7 vs E 38.6 | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/argyle-vs-worklio" }, "tokens": { "markdown": 2200, "slim": 730 }, "version": 1 }