# Argyle > 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. - Canonical: https://www.anchorterminal.com/tools/argyle - Markdown: https://www.anchorterminal.com/tools/argyle.md (~8,350 tokens) - Slim: https://www.anchorterminal.com/tools/argyle.min.md (~1,980 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/argyle.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade 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 | Field | Value | | --- | --- | | Vendor | Argyle Systems Inc. (https://www.argyle.com) | | Kind | HTTP API | | Category | Payroll infrastructure (https://www.anchorterminal.com/categories/payroll) | | Transport | HTTP | | Endpoint | `https://api.argyle.com/v2` | | Auth | API key · 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 (Paid) · 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). | | x402 | No · No x402, MPP or L402 in the documentation index, the OpenAPI specification or the vendor's site (checked 2026-10-08). | | Licence | Proprietary service under Argyle's Open Payroll Customer Terms. The React Native Link SDK on npm is Apache 2.0 | | Packages | npm: `@argyleio/argyle-plugin-react-native` | | Source | https://github.com/argyle-systems/argyle-link-react-native | | Docs | https://docs.argyle.com | | llms.txt | https://docs.argyle.com/llms.txt | | Last release | 2026-10-01 | | npm downloads / week | 481 | | 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 | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/argyle.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 81 | 16.2 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 86 | 14.0 | | Agent ergonomics | 13% | 16.2 | 58 | 9.4 | | Security & auth | 14% | 17.5 | 48 | 8.4 | | Payments & pricing | 10% | 12.5 | 15 | 1.9 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 75 | 6.6 | | Transparency & trust (editorial 68, provenance 97) | 7% | 8.8 | 83 | 7.3 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **63.7 → B** | ### Why each score - Reliability 81: Read with the hosted lines and scored on the REST API. status.argyle.com lists seven components with incident history (20). One incident in the 90 days to 8 October 2026. On 6 October Item search in Link and the API was slow from 17:16 to 19:28 UTC, with a fix applied by 18:15. The page marks it major, but it was degraded search and not an API outage, so this reads as minor incidents only (20). The feed's older entries all carry a creation date of 15 September 2026 and resolution dates from 2022 to December 2023, so the record between those dates could not be confirmed. The limit is published as 50 requests a second (15). The docs say to queue rate-limited requests and avoid immediate retry loops. No `Retry-After` header is documented and no idempotency keys were found for the POST endpoints (6 of 15). Service Levels commit to 99 per cent monthly availability with credits, on commercially reasonable efforts (10). The API carries no beta label (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 86: One OpenAPI 3.0 file at docs.argyle.com/openAPI/argyle-all.yaml with 91 operations and 119 schemas (25). llms.txt and scoped indexes list the guides and reference, each page is served as Markdown, and llms-full.txt holds the whole set (10). Every operation has a description, and a guide explains when to use Verifications and when the Data APIs. Many operation descriptions are one line (15 of 20). Schemas carry 127 enums and 157 required lists (12 of 15). The file has 222 examples and the guides give curl and JSON samples. It documents an error response on only 2 of 91 operations, with errors covered by a status code table and two connection error catalogues (9 of 15). The version is in the path as `/v2`, and a dated public changelog covers API changes (15). - Agent ergonomics 58: `limit` sizes list responses, 10 by default and 200 at most, and reports summarise an account's records. No per-request field selection was found (15 of 25). Cursor paging on every list endpoint, with filters by user, account, employment and date range on the data endpoints (18 of 20). Errors carry a `detail` string or per-field lists, a status code table is published, and connection errors have named codes with causes. General API errors have no machine code. We saw the `detail` shape and an `x-trace-id` header on a live unauthenticated request (13 of 20). No idempotency keys were found. Most of the API is GET, and `external_id` lets a caller find a user before creating a duplicate (5 of 20). Few required parameters on reads. The official SDKs are Link front ends for five platforms, with no server-side client found (7 of 15). - Security & auth 48: API keys are an ID and secret pair sent by HTTP Basic auth, never in the URL. Any number of named keys can be created per environment and deleted, and the secret is shown once. No per-key scopes or expiry were found (20 of 30). A worker grants each payroll connection through Link and can remove it, and the Console API developer role is kept from personal data. No read-only key was found, and deletes of users, accounts and reports take effect with no confirmation step (10 of 20). Responses carry text from payroll platforms and OCR of uploaded documents. The AI tools page says to keep keys and user data out of prompts, with no guidance on injected text (3 of 15). The sub-processor list mentions in-product audit log data, and responses carry a trace ID. No audit log page or API was found in the reviewed documentation (5 of 15). security.txt is valid with a PGP key, Security Measures are published and the DPA commits to an annual external audit with summaries on request. The trust centre could not be read, no bug bounty was found, and the terms forbid customers running security tests (10 of 20). - Payments & pricing 15: Read with the hosted rubric. No x402, MPP or L402 (0). No prices are published. The site has no pricing page and fees are set in a Service Order (0). A Sandbox with sample data comes with a Console sign-up, and the sign-up page shows no card step. It reaches no real payroll account, and the size of the trial allowance for real connections is not stated, so partial credit (15 of 20). A person signs up in a browser, and a worker must sign in through Link for every connection (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 75: The changelog's latest entries are dated 1 October 2026 (30). Twelve dated entries between 14 July and 1 October 2026 (20). Closed service with a dated changelog that takes subscriptions, and a Support Policy with acknowledgement targets from one business hour. We could not test whether support answers (11 of 15). The Link SDKs are current for React Native (5.15.5, 13 May 2026), iOS (5.15.2) and Flutter (1.14.2). The public Android repository's last commit is 1 August 2024, no server-side SDK was found, and the official MCP registry has no Argyle entry (8 of 15). The React Native repository had dependency updates up to 21 July 2026. We could not confirm the CI result (6 of 10). - Transparency & trust 83: Closed service. The Customer Terms, DPA, Service Levels, Support Policy and sub-processor list are public and dated 1 October 2026, and the React Native SDK is Apache 2.0 (17 of 30). The DPA commits to deleting customer data within 90 days of termination and to breach notice within 72 hours. The Privacy Notice says records are deleted when the worker ends a connection and otherwise kept no longer than reasonably necessary, with no fixed periods. It lets Argyle create aggregated and de-identified information from records and give it to others for any lawful purpose (21 of 30). A compatibility section defines breaking changes, and the terms give a customer a cure period and a right to terminate after a modification that harms it. No notice period before a breaking change was found, and ending support for a payroll platform is excluded (10 of 20). The sub-processor list names 20 vendors with locations, and the DPA promises 30 days' notice of additions (20 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (18 items): https://www.anchorterminal.com/fixes/argyle.md (JSON https://www.anchorterminal.com/fixes/argyle.json) ### What we couldn't check - unchecked: the trust centre at trust.argyle.com. It is drawn by script and our reader saw only the title, so no SOC 2 or ISO 27001 report could be confirmed - unchecked: live API behaviour beyond one unauthenticated request. We had no Sandbox credentials, so limits, paging and webhooks are as documented - unchecked: whether Console sign-up issues a Sandbox key at once and whether a card is asked for. Console sits behind a login - unchecked: the number of free real connections in trial mode today. The only figure found, five, is from a changelog entry dated 2 April 2022 - unchecked: whether 429 responses carry a `Retry-After` header in practice. None is documented - unchecked: the status record between December 2023 and September 2026. The incident feed's older entries were imported on 15 September 2026 - unchecked: GitHub stars, open issues and CI results for the Link SDK repositories, and whether the Android SDK is released somewhere other than its public repository - No privacy policy for business customers was found. `provenance.privacy` points at the Privacy Notice that governs workers' records, and customer data falls under the Data Protection Addendum - The lead was right on the vendor, the interface and the sandbox. The MCP server Argyle documents is a documentation search server and does not reach the API ### Sources - documentation index for agents: (seen 2026-10-08) - full documentation text: (seen 2026-10-08) - OpenAPI specification: (seen 2026-10-08) - API guide (auth, limits, errors, paging, compatibility): (seen 2026-10-08) - webhooks: (seen 2026-10-08) - AI tools and docs MCP server: (seen 2026-10-08) - docs MCP server tool list: (seen 2026-10-08) - sandbox testing: (seen 2026-10-08) - data security: (seen 2026-10-08) - API keys in Console: (seen 2026-10-08) - Console roles: (seen 2026-10-08) - API reference index: (seen 2026-10-08) - changelog: (seen 2026-10-08) - unauthenticated request to the Sandbox API: (seen 2026-10-08) - status incidents: (seen 2026-10-08) - status components: (seen 2026-10-08) - Open Payroll Customer Terms: (seen 2026-10-08) - Data Protection Addendum: (seen 2026-10-08) - Service Levels: (seen 2026-10-08) - Support Policy: (seen 2026-10-08) - sub-processor list: (seen 2026-10-08) - Privacy Notice: (seen 2026-10-08) - Security Measures: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - home page (pricing redirect): (seen 2026-10-08) - Console sign-up page: (seen 2026-10-08) - npm package: (seen 2026-10-08) - React Native Link SDK source: (seen 2026-10-08) - Android Link SDK source: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - domain registration: (seen 2026-10-08) ## Who's behind it (provenance 97/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Argyle Systems Inc. | 20/20 | | Domain age | argyle.com, registered 1997-06-08 (29 years) | 15/15 | | Endpoint on the vendor's domain | api.argyle.com | 15/15 | | Terms of service | read, states 7 of the 7 things a reader expects, and has 1 clause that costs points | 8/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.argyle.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.argyle.com/legal/open-payroll/customer-terms), read 2026-10-08, dated 2026-10-01, states 7 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "(vi) use the Open Payroll Platform to develop a product or service that competes with the Open Payroll Platform." - To know. Says access can be ended without notice or for any reason. "(i) Service Orders. Either party may terminate an Online Order for convenience on notice to the other party." - To know. Requires arbitration or waives class actions. "Before initiating arbitration, a party must give the other party written notice describing the dispute and the relief sought, and the parties must attempt in good faith to resolve it through discussions between representatives with authority to settle it." - Gives the date it was last updated. Last updated 2026-10-01. - Names the governing law or courts. The law of the State of New York. - States a limit on its liability. Capped at US$1,000. - Says how changes to the terms are announced. Says it gives notice of a change. - Also in the text (2026-10-08). Unless a Service Order says otherwise, Argyle may list the customer publicly and use its name, marks and logos for marketing. "Argyle may publicly list Customer as a customer of Argyle and use Customer’s name, trademarks, service marks, trade names, and logos for marketing or promotional purposes" - Also in the text (2026-10-08). Argyle may change the fees for requests routed through third-party platforms on 30 days notice. "Argyle may adjust the Fees for Routed Requests on thirty (30) days’ notice to Customer to reflect changes in Argyle’s costs of providing Routed Requests, effective for Routed Requests submitted after that notice period ends." - Also in the text (2026-10-08). The customer may integrate the API with its own applications only if it tells Argyle about each integration, naming the application, before it goes live. "provided Customer gives Argyle notice of each such integration with a Customer Application (including identifying that Customer Application) before its go-live." **Privacy policy** (https://www.argyle.com/legal/consumers/privacy-notice), read 2026-10-08, dated 2026-10-01, states 7 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2026-10-01. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacy@argyle.com. - Not found in the text. Says where data is transferred or stored. - Also in the text (2026-10-08). Argyle may create aggregated and de-identified information from consumer records and give it to others for any lawful purpose. "We may also create de-identified information from Your Records and Direction Records, and we take reasonable measures to ensure it cannot be associated with you or your household." - Also in the text (2026-10-08). Records of what a consumer authorised are kept after the source records are deleted, and may be kept indefinitely. "Asking us to delete Your Records does not delete your Direction Records, and we may keep them indefinitely." - Also in the text (2026-10-08). The notice does not cover records Argyle processes on behalf of a business customer, which fall under that customer’s own notice and its agreement with Argyle. "that processing is governed by that customer’s notice and its agreement with Argyle, not by this Privacy Notice." ## Live (updated 2026-10-08 22:39 UTC) - Right now: up, HTTP 404, 194 ms, checked 2026-10-08 22:39 UTC (get on `https://api.argyle.com/v2`) - Uptime 24h 100.0% (36 probes) · 30 days 100.0% (36 probes) · p50 205 ms · p95 315 ms - Vendor status page: none, All Systems Operational - Always current: https://www.anchorterminal.com/api/v1/live/argyle.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## 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 ## Before you call it (notes for agents) 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 First request: ```bash curl https://api-sandbox.argyle.com/v2/accounts \ -u api_key_id:api_key_secret ``` Through letme (picks today, calling later): https://letme.dev/argyle. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Finch | BB | 71.6 | 104 | payroll.employees, payroll.contractors | no | https://www.anchorterminal.com/tools/finch.md | | Check | B | 67.5 | 208 | payroll.employees, payroll.contractors | no | https://www.anchorterminal.com/tools/check-payroll.md | | Gusto | B | 63.3 | 314 | payroll.employees, payroll.contractors | no | https://www.anchorterminal.com/tools/gusto.md | | Everee | C | 55.1 | 519 | payroll.employees, payroll.contractors | no | https://www.anchorterminal.com/tools/everee.md | | Employment Hero Payroll | D | 50.4 | 591 | payroll.employees, payroll.contractors | no | https://www.anchorterminal.com/tools/employment-hero.md | | Salsa | D | 46.1 | 651 | payroll.employees, payroll.contractors | no | https://www.anchorterminal.com/tools/salsa.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The API uses HTTP Basic auth with an API key ID and secret, at `https://api-sandbox.argyle.com/v2` for Sandbox and `https://api.argyle.com/v2` for Production (source: ) - The consolidated OpenAPI 3.0 file (version 1.0.112) has 91 operations, 54 of them GET, including 23 under `/partners/v2` (source: ) - The rate limit is 50 requests a second, list endpoints take `limit` up to 200 with cursor paging, and the docs say not to request pages in parallel (source: ) - Service Levels dated 1 October 2026 commit to commercially reasonable efforts for 99 per cent monthly availability, with credits of 10, 25 or 100 per cent of usage fees (source: ) - status.argyle.com lists one incident in the 90 days to 8 October 2026, slow Item search in Link and the API on 6 October, marked major and resolved in about two hours (source: ) - Webhooks are signed with HMAC-SHA512 in `X-Argyle-Signature` only when the subscription sets a `secret`, and a failed delivery is retried once after 30 seconds (source: ) - The docs MCP server at `https://docs.argyle.com/mcp` has three tools for searching and reading the documentation and sending feedback. It does not call the Argyle API (source: ) - Banking verifications are resold. The sub-processor list says the Open Banking Platform is run by Finicity (source: ) - The Customer Terms grant a licence for the platform to legal entities only, forbid security or vulnerability tests by customers, and say Argyle is not acting as a consumer reporting agency (source: ) ## Compare - [Argyle vs Check](https://www.anchorterminal.com/compare/argyle-vs-check-payroll.md): B 63.7 vs B 67.5 - [Argyle vs Employment Hero Payroll](https://www.anchorterminal.com/compare/argyle-vs-employment-hero.md): B 63.7 vs D 50.4 - [Argyle vs Everee](https://www.anchorterminal.com/compare/argyle-vs-everee.md): B 63.7 vs C 55.1 - [Argyle vs Finch](https://www.anchorterminal.com/compare/argyle-vs-finch.md): B 63.7 vs BB 71.6 - [Argyle vs Gusto](https://www.anchorterminal.com/compare/argyle-vs-gusto.md): B 63.7 vs B 63.3 - [Argyle vs Paychex](https://www.anchorterminal.com/compare/argyle-vs-paychex.md): B 63.7 vs E 44.8 - [Argyle vs Salsa](https://www.anchorterminal.com/compare/argyle-vs-salsa.md): B 63.7 vs D 46.1 - [Argyle vs Zeal](https://www.anchorterminal.com/compare/argyle-vs-zeal.md): B 63.7 vs E 45.4 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on argyle.com or one of its subdomains, or the README of github.com/argyle-systems/argyle-link-react-native. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "argyle", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Argyle on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Argyle on Anchor Terminal](https://www.anchorterminal.com/badges/argyle.svg)](https://www.anchorterminal.com/tools/argyle) ``` Plain link: ```html Argyle on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Argyle is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/argyle-dark.png - Light: https://www.anchorterminal.com/assets/share/argyle-light.png