Argyle
Argyle is an employment data connectivity platform offering a REST API for accessing payroll records, employment history, income verification, and gig platform earnings via user-consented direct-source connections. The API provides real-time access to standardized payroll data across traditional employers, gig platforms, and government payroll systems, with webhook alerts for employment and income changes.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Argyle the way a machine reads it — 225 machine-readable artifacts across 26 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Argyle scores 55.3/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Argyle
Each block below is one kind of artifact we hold for Argyle. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 26
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Argyle Accounts API
The Accounts API from Argyle — 3 operation(s) for accounts.
Argyle Deposit Destinations API
The Deposit Destinations API from Argyle — 2 operation(s) for deposit destinations.
Argyle Employer Search API
The Employer Search API from Argyle — 1 operation(s) for employer search.
Argyle Employments API
The Employments API from Argyle — 1 operation(s) for employments.
Argyle Gigs API
The Gigs API from Argyle — 2 operation(s) for gigs.
Argyle Identities API
The Identities API from Argyle — 2 operation(s) for identities.
Argyle Invites API
The Invites API from Argyle — 3 operation(s) for invites.
Argyle Item Filters API
The Item Filters API from Argyle — 2 operation(s) for item filters.
Argyle Item Migrations API
The Item Migrations API from Argyle — 1 operation(s) for item migrations.
Argyle Items API
The Items API from Argyle — 2 operation(s) for items.
Argyle Open Banking API
The Open Banking API from Argyle — 6 operation(s) for open banking.
Argyle Partners API
The Partners API from Argyle — 15 operation(s) for partners.
Argyle Payroll Documents API
The Payroll Documents API from Argyle — 2 operation(s) for payroll documents.
Argyle Paystubs API
The Paystubs API from Argyle — 2 operation(s) for paystubs.
Argyle Ratings API
The Ratings API from Argyle — 2 operation(s) for ratings.
Argyle Receipts API
The Receipts API from Argyle — 1 operation(s) for receipts.
Argyle Reports API
The Reports API from Argyle — 3 operation(s) for reports.
Argyle Sessions API
The Sessions API from Argyle — 1 operation(s) for sessions.
Argyle Shifts API
The Shifts API from Argyle — 2 operation(s) for shifts.
Argyle User Forms API
The User Forms API from Argyle — 2 operation(s) for user forms.
Argyle User Tokens API
The User Tokens API from Argyle — 1 operation(s) for user tokens.
Argyle User Uploads API
The User Uploads API from Argyle — 2 operation(s) for user uploads.
Argyle Users API
The Users API from Argyle — 2 operation(s) for users.
Argyle Vehicles API
The Vehicles API from Argyle — 2 operation(s) for vehicles.
Argyle Verifications API
The Verifications API from Argyle — 4 operation(s) for verifications.
Argyle Webhooks API
The Webhooks API from Argyle — 1 operation(s) for webhooks.
Scroll within the panel for all 26 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Argyle GraphQL Schema
Conceptual GraphQL schema for the Argyle income and employment verification API.
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Argyle Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Argyle Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Argyle Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Argyle Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Argyle API Rules
SPECTRALJSON Schema 99
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Account
JSON SCHEMAAddress
JSON SCHEMAAvailabilityItem
JSON SCHEMABankingReport
JSON SCHEMABankingReportCustomField
JSON SCHEMABankingReportRequest
JSON SCHEMABasePay
JSON SCHEMAClientAddress
JSON SCHEMAClientBirthDate
JSON SCHEMAClientCreateUserResponse
JSON SCHEMAClientOpenBanking
JSON SCHEMAClientOpenBankingEndUser
JSON SCHEMAClientReportCustomField
JSON SCHEMAClientSession
JSON SCHEMAClientSessionConfiguration
JSON SCHEMAClientSessionCreateConfiguration
JSON SCHEMAClientSessionCreateRequest
JSON SCHEMAClientUser
JSON SCHEMAClientUserCreateRequest
JSON SCHEMAClientUserUpdateRequest
JSON SCHEMAClientVerification
JSON SCHEMAClientVerificationBilling
JSON SCHEMAClientVerificationCreateReportRequest
JSON SCHEMAClientVerificationCreateRequest
JSON SCHEMAClientVerificationEmployment
JSON SCHEMAClientVerificationEmploymentRequest
JSON SCHEMAClientVerificationError
JSON SCHEMAClientVerificationErrorResource
JSON SCHEMAClientVerificationListResponse
JSON SCHEMAClientVerificationLoan
JSON SCHEMAClientVerificationRefreshReportRequest
JSON SCHEMAClientVerificationRefreshRequest
JSON SCHEMAClientVerificationReport
JSON SCHEMAClientVerificationReportConfiguration
JSON SCHEMAClientVerificationStatus
JSON SCHEMAClientVerificationUpdateRequest
JSON SCHEMACreateUserTokenRequest
JSON SCHEMACreateUserTokenResponse
JSON SCHEMADeduction
JSON SCHEMADepositDestination
JSON SCHEMADestination
JSON SCHEMAEmployer
JSON SCHEMAEmployment
JSON SCHEMAFilingStatus
JSON SCHEMAGig
JSON SCHEMAGrossPay
JSON SCHEMAGrossPayTotal
JSON SCHEMAIdentity
JSON SCHEMAInviteDelivery
JSON SCHEMAInviteObject
JSON SCHEMAItem
JSON SCHEMAOpenBankingBankAccount
JSON SCHEMAPartnerAddress
JSON SCHEMAPartnerBirthDate
JSON SCHEMAPartnerCreateUserResponse
JSON SCHEMAPartnerOpenBanking
JSON SCHEMAPartnerOpenBankingEndUser
JSON SCHEMAPartnerPaystub
JSON SCHEMAPartnerReportCustomField
JSON SCHEMAPartnerSession
JSON SCHEMAPartnerSessionConfiguration
JSON SCHEMAPartnerSessionCreateConfiguration
JSON SCHEMAPartnerSessionCreateRequest
JSON SCHEMAPartnerUser
JSON SCHEMAPartnerUserCreateRequest
JSON SCHEMAPartnerUserUpdateRequest
JSON SCHEMAPartnerUserUpload
JSON SCHEMAPartnerVerification
JSON SCHEMAPartnerVerificationBilling
JSON SCHEMAPartnerVerificationCreateReportRequest
JSON SCHEMAPartnerVerificationCreateRequest
JSON SCHEMAPartnerVerificationCreationFailedContext
JSON SCHEMAPartnerVerificationEmployment
JSON SCHEMAPartnerVerificationEmploymentRequest
JSON SCHEMAPartnerVerificationError
JSON SCHEMAPartnerVerificationErrorResource
JSON SCHEMAPartnerVerificationListResponse
JSON SCHEMAPartnerVerificationLoan
JSON SCHEMAPartnerVerificationRefreshReportRequest
JSON SCHEMAPartnerVerificationRefreshRequest
JSON SCHEMAPartnerVerificationReport
JSON SCHEMAPartnerVerificationReportConfiguration
JSON SCHEMAPartnerVerificationStatus
JSON SCHEMAPartnerVerificationUpdateRequest
JSON SCHEMAPartnerVerificationWebhookMessage
JSON SCHEMAPartnerWebhookSubscriptionRequest
JSON SCHEMAPayrollDocument
JSON SCHEMAPaystub
JSON SCHEMAPlatformIds
JSON SCHEMARating
JSON SCHEMAReport
JSON SCHEMASendInviteRequest
JSON SCHEMAShift
JSON SCHEMATax
JSON SCHEMAUser
JSON SCHEMAUserForm
JSON SCHEMAUserUpload
JSON SCHEMAVehicle
JSON SCHEMAScroll within the panel for all 99 ·
Examples 90
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Get V2 Accounts Response 200
EXAMPLEGet V2 Gigs Response 200
EXAMPLEGet V2 Invites Response 200
EXAMPLEGet V2 Items Response 200
EXAMPLEGet V2 Ratings Response 200
EXAMPLEGet V2 Reports Response 200
EXAMPLEGet V2 Shifts Response 200
EXAMPLEGet V2 Users Response 200
EXAMPLEGet V2 Vehicles Response 200
EXAMPLEListemployers Response 200
EXAMPLEPatch V2 Users {Id} Request
EXAMPLEPost V2 Invites Response 200
EXAMPLEPost V2 Item Filters Request
EXAMPLEPost V2 Receipts Request
EXAMPLEPost V2 Users Request
EXAMPLEPost V2 Users Response 200
EXAMPLEScroll within the panel for all 90 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Argyle — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/argyle · machine-readable index on apis.io