argyle.com valid

Argyle Docs

Argyle documentation for integrating real-time income, employment, payroll document, and banking data into verification workflows. Use this index to find the right guide, Link page, API reference, integration guide, or OpenAPI specification.

For agents: Argyle docs for real-time income, employment, payroll and banking data APIs used in verification workflows; includes API reference and OpenAPI spec.

income verificationpayroll data apiemployment verificationbank dataopenapi

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:21:34.339Z. Cached copy · Source on argyle.com

# Argyle Docs

> Argyle documentation for integrating real-time income, employment, payroll document, and banking data into verification workflows. Use this index to find the right guide, Link page, API reference, integration guide, or OpenAPI specification.

Important context:
- Payroll VOIE uses connected payroll account data for income and employment verification.
- Doc VOI uses uploaded payroll and identity documents, with OCR and authenticity support where available.
- Banking VOI and VOA use bank-authenticated data for income and asset workflows.
- Link is the user-facing account connection experience. Banking connection flows use session URLs with the banking SDK or an enabled hosted experience.
- Use Sandbox for testing sample users and simulated flows before using Production.
- Prefer the `.md` page links in these indexes for page content; use OpenAPI YAML for generated endpoint schemas.

Common integration flows:
- Payroll Data API flow: create a user, launch Link with a user token, listen for account and data webhooks, then retrieve identities, paystubs, or payroll documents.
- Report flow: use Verifications for new report implementations. Order a verification, complete the required account-connection or document steps, monitor verification webhooks, then retrieve the report.
- Banking flow: order a banking verification, create a banking session, let the user connect their accounts, then track verification status and retrieve the report.

## Guides

- [Guides](https://docs.argyle.com/guides.md): Choose how you want to build with Argyle.
- [Overview llms.txt](https://docs.argyle.com/overview/llms.txt): Scoped index for product overview, data structure, security, and sandbox testing.
- [Verifications llms.txt](https://docs.argyle.com/verifications/llms.txt): Scoped index for verification implementation, lifecycle, results, recovery, testing, and platform partners.
- [Data APIs llms.txt](https://docs.argyle.com/data-apis/llms.txt): Scoped index for direct data access, delivery readiness, and ongoing refresh.
- [Workflows llms.txt](https://docs.argyle.com/workflows/llms.txt): Scoped index for account connection, reconnection, and document processing workflows.
- [How Argyle Works](https://docs.argyle.com/overview/how-argyle-works.md): Argyle helps consumers share income and employment data straight from the source.
- [Verifications vs. Data APIs](https://docs.argyle.com/overview/verifications-vs-data-apis.md): Choose a report workflow or retrieve the individual records your application needs.
- [Data Sets](https://docs.argyle.com/overview/data-structure/data-sets.md): Payroll data and documents from connected accounts.
- [Data Delivery](https://docs.argyle.com/overview/data-delivery.md): Know when payroll data is ready.
- [Sandbox Testing](https://docs.argyle.com/overview/sandbox-testing.md): Explore the Sandbox environment.

## Verticals

- [Verticals llms.txt](https://docs.argyle.com/verticals/llms.txt): Scoped index for mortgage, tenant
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=argyle.com · GET /v1/domain/argyle.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for argyle.com:
1. POST https://agentwebmap.com/v1/sites/argyle.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://argyle.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/argyle.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/argyle.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.