# Argyle (slim)

> 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.

- Full: https://www.anchorterminal.com/tools/argyle.md (~8,350 tokens) · this version ~1,980 tokens · JSON https://www.anchorterminal.com/tools/argyle.json · canonical https://www.anchorterminal.com/tools/argyle
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-08

**B · 63.7/100 · rank #297 of 722 · #3 in Payroll infrastructure · not agent-ready · confidence medium**


Assessment: 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.

## Facts

- Kind: HTTP API · vendor: Argyle Systems Inc. · category: Payroll infrastructure · legal entity: Argyle Systems Inc. · provenance 97/100
- Endpoint: `https://api.argyle.com/v2` (HTTP)
- Auth: API key · pricing: Paid · x402: no · licence: Proprietary service under Argyle's Open Payroll Customer Terms. The React Native Link SDK on npm is Apache 2.0
- Probe metrics: not measured yet (probes haven't run)
- Surface graded: The REST API at `https://api.argyle.com/v2`, which carries no beta label. The docs MCP server is a documentation search tool and is not graded as the product
- What it reads: Identities, employments, paystubs, payroll documents, deposit destinations, shifts, gigs, vehicles and ratings from a worker's connected payroll or gig account, plus uploaded documents with OCR. Argyle does not run payroll and no write to the payroll account is in the specification
- Verifications: `POST /v2/verifications` orders a payroll, banking or document income report through one lifecycle, with `/v2/sessions` for the embedded or invited connection step and PDF or JSON reports. The older `/v2/reports` flow is marked deprecated in the docs
- Credentials: API key ID and secret per environment, created in Console, with the secret shown once. Any number of named keys, each deletable. User tokens for Link and session links expire after one hour
- Consent: The worker signs in to the payroll account through Argyle Link (embedded, hosted or by emailed or texted invite) and can remove the connection through Link or Argyle Passport
- Environments: Sandbox at `https://api-sandbox.argyle.com/v2` with three sample users (deleted after 60 days) and a simulated refresh endpoint. Production at `https://api.argyle.com/v2`. Receipts are Production only
- Rate limits: 50 requests a second. 429 above the limit, with guidance to queue and retry later
- Pagination and filters: Cursor paging on every list endpoint, `limit` 10 by default and 200 at most. Filters by `user`, `account`, `employment` and date range on the data endpoints
- Errors: `detail` string for general errors and per-field lists for validation errors, a status code table including 520 for an upstream platform error, catalogues of account and bank connection error codes, and an `x-trace-id` response header
- Webhooks: Subscriptions by `POST /v2/webhooks` or Console, apply to every event the key can see, optional HMAC-SHA512 signature, four static sender IP addresses, one retry after 30 seconds
- Versioning: `/v2` in the path, OpenAPI file version 1.0.112, and a written list of breaking and non-breaking changes. Changes are announced at changelog.argyle.com
- SDKs: Link SDKs only, for web, iOS (5.15.2), Android, React Native (`@argyleio/argyle-plugin-react-native` 5.15.5, 13 May 2026, Apache 2.0) and Flutter (1.14.2). No server-side API client was found. A Postman collection is documented
- Console roles: Admin, Full member, Operations, Operations (limited) and API developer. The API developer role reaches API keys and connection metadata but not personal user data
- Service levels: 99 per cent monthly availability on commercially reasonable efforts, credits on written request within 30 days, third-party and payroll platform outages excluded. Support Policy sets a one business hour acknowledgement for Priority 1 errors
- Status: status.argyle.com with components for Payroll, Banking, Documents, API, Console and Third-party integrations among others
- Sub-processors: 20 named, with Google Cloud Platform in the United States for hosting, and Cloudflare, Confluent, Databricks, HotJar, Looker, Ocrolus (United States and India), SendGrid, Sentry and Twilio for the platform. 30 days' notice of additions through the changelog

- Scores: Reliability 81, Performance pending, Schema & documentation 86, Agent ergonomics 58, Security & auth 48, Payments & pricing 15, Task success pending, Maintenance & community 75, Transparency & trust 83 · total over the 7 assessed categories
- Why: Reliability, Read with the hosted lines and scored on the REST API. · Schema & documentation, One OpenAPI 3.0 file at docs.argyle.com/openAPI/argyle-all.yaml with 91 operations and 119 schemas (25). · Agent ergonomics, `limit` sizes list responses, 10 by default and 200 at most, and reports summarise an account's records. · Security & auth, API keys are an ID and secret pair sent by HTTP Basic auth, never in the URL. · Payments & pricing, Read with the hosted rubric. · Maintenance & community, The changelog's latest entries are dated 1 October 2026 (30). · Transparency & trust, Closed service.
- Sources: 31, open questions: 9, both in the full twin
- Capabilities: payroll.employees, payroll.contractors
- JSON: https://www.anchorterminal.com/api/v1/tools/argyle.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/argyle.svg` or a link to https://www.anchorterminal.com/tools/argyle from a page on argyle.com or one of its subdomains, or the README of github.com/argyle-systems/argyle-link-react-native, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. 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
2. 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
3. Do not read data straight after an account connects. Wait for the account and data webhooks, or for the verification status, before fetching records
4. 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
5. Stay under 50 requests a second. On 429, queue the request and retry later, not at once
6. Treat `DELETE /v2/users/{id}` as permanent. It removes every resource tied to that user, with no confirmation step

## Connect

```bash
curl https://api-sandbox.argyle.com/v2/accounts \
  -u api_key_id:api_key_secret
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/argyle

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Finch | BB | 71.6 | payroll.employees, payroll.contractors | https://www.anchorterminal.com/tools/finch.min.md |
| Check | B | 67.5 | payroll.employees, payroll.contractors | https://www.anchorterminal.com/tools/check-payroll.min.md |
| Gusto | B | 63.3 | payroll.employees, payroll.contractors | https://www.anchorterminal.com/tools/gusto.min.md |
| Everee | C | 55.1 | payroll.employees, payroll.contractors | https://www.anchorterminal.com/tools/everee.min.md |
| Employment Hero Payroll | D | 50.4 | payroll.employees, payroll.contractors | https://www.anchorterminal.com/tools/employment-hero.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)