DailyPay

DailyPay is an on-demand pay (earned wage access) platform that lets employees access wages they have already earned before the scheduled payday. The company sells to employers across healthcare, retail, restaurants, manufacturing, hospitality and the public sector, and integrates with 180+ HCM, payroll and time-management systems. Its developer surface — the DailyPay REST API — is a json:api-shaped OAuth 2.0 / OpenID Connect API covering people, jobs, organizations, paychecks, accounts (including the EARNINGS_BALANCE account that carries available earnings), transfers and PCI-scoped debit-card tokenization, complemented by DailyPay Elements, a set of hosted drop-in iframe components for embedding on-demand pay into partner applications.

DailyPay publishes 1 API on the APIs.io network: Rest API. Tagged areas include Company, Payments, Payroll, Human Resources, and Earned Wage Access.

DailyPay’s developer surface includes documentation, API reference, getting-started guide, authentication, support, engineering blog, signup flow, and 33 more developer resources.

🌐 Visit website 📡 Source on GitHub

60.6/100 strong ▬ flat Agent 47/100 agent native Full breakdown ↓
scored 2026-08-24 · rubric v0.13.0

1 APIs 1 MCP Servers

Company Payments Payroll Human Resources Earned Wage Access On-Demand Pay Financial-Services Fintech Money Transfer Benefits

Kin Score

Kin Score How this is scored →
scored 2026-08-24 · rubric v0.13.0

Composite quality — 60.6/100 · strong

Contract Quality 11.9 / 21

Developer Ergonomics 12.4 / 17

Access Clarity 8.5 / 17

Operational Transparency 3.2 / 11

Contract Governance 3.1 / 10

Discoverability 7.4 / 9

Regulatory Posture 10.8 / 15

Agent readiness — 47/100 · agent native

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/dailypay: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

DailyPay Rest API

Embed DailyPay and On Demand Pay features into your application. A json:api-compliant REST API covering jobs, accounts, transfers, paychecks, organizations, people and debit-car...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Scopes 1

OAuth scopes governing access to this provider's APIs.

Dailypay Scopes

5 scopes · clientCredentials/authorizationCode

5 scopes

SCOPES

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

WellKnown

MCPServer

LLMsTxt

AgenticAccess

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Lifecycle

Conventions

Idempotency

ErrorCatalog

DataModel

Conformance

Components

Scroll for all 7

Build 5

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

DeclineCodes

ToolCrosswalk

Access & Security 7

Authentication, authorization, and security posture

Authentication

OAuthScopes

Compliance

TrustCenter

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Scroll for all 7

Operate 3

Status, limits, changes, and where to get help

Support

Support

HelpCenter

HelpCenter

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Other 1

Properties that don't map to a standard resource type

OpenIDConnect

OpenIDConnect

Source (apis.yml)

aid: dailypay
name: DailyPay
description: DailyPay is an on-demand pay (earned wage access) platform that lets employees access wages they have already
  earned before the scheduled payday. The company sells to employers across healthcare, retail, restaurants, manufacturing,
  hospitality and the public sector, and integrates with 180+ HCM, payroll and time-management systems. Its developer surface
  — the DailyPay REST API — is a json:api-shaped OAuth 2.0 / OpenID Connect API covering people, jobs, organizations, paychecks,
  accounts (including the EARNINGS_BALANCE account that carries available earnings), transfers and PCI-scoped debit-card tokenization,
  complemented by DailyPay Elements, a set of hosted drop-in iframe components for embedding on-demand pay into partner applications.
url: https://raw.githubusercontent.com/api-evangelist/dailypay/refs/heads/main/apis.yml
image: https://developer.dailypay.com/static/svgs/dp_text.svg
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline
specificationVersion: '0.23'
created: '2026-08-01'
modified: '2026-08-01'
x-enrichment:
  date: '2026-08-01'
  status: enriched
  artifacts_added: 30
  pass: local-v1
tags:
- Company
- Payments
- Payroll
- Human Resources
- Earned Wage Access
- On-Demand Pay
- Financial-Services
- Fintech
- Money Transfer
- Benefits
tags_raw:
- Company
- Payments
- Payroll
- Human Resources
- Earned Wage Access
- On-Demand Pay
- Financial Services
- Fintech
- Money Transfer
- Benefits
apis:
- aid: dailypay:dailypay-rest-api
  name: DailyPay Rest API
  description: Embed DailyPay and On Demand Pay features into your application. A json:api-compliant REST API covering jobs,
    accounts, transfers, paychecks, organizations, people and debit-card tokenization, secured with OAuth 2.0 client-credentials
    and authorization-code (PKCE) flows, versioned by the DailyPay-API-Version header and requiring an Idempotency-Key on
    transfer creation.
  humanURL: https://developer.dailypay.com/products/rest/reference
  baseURL: https://api.dailypay.com/rest
  tags:
  - Job
  - Account
  - Transfers
  - Paychecks
  - Organization
  - People
  - Card Tokenization
  - Health
  tags_raw:
  - Jobs
  - Accounts
  - Transfers
  - Paychecks
  - Organizations
  - People
  - Card Tokenization
  - Health
  properties:
  - type: OpenAPI
    url: openapi/dailypay-rest-openapi-original.yml
  - type: Documentation
    url: https://developer.dailypay.com/products/rest
  - type: APIReference
    url: https://developer.dailypay.com/products/rest/reference
  - type: Overlay
    url: overlays/dailypay-rest-overlay.yaml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.dailypay.com/
- type: DeveloperPortal
  url: https://developer.dailypay.com/
- type: Documentation
  url: https://developer.dailypay.com/products/rest
- type: APIReference
  url: https://developer.dailypay.com/products/rest/reference
- type: GettingStarted
  url: https://developer.dailypay.com/products/rest/guides/auth
- type: Authentication
  url: authentication/dailypay-authentication.yml
- type: OAuthScopes
  url: scopes/dailypay-scopes.yml
- type: OpenIDConnect
  url: https://auth.dailypay.com/.well-known/openid-configuration
- type: Support
  url: https://www.dailypay.com/contact/
- type: HelpCenter
  url: https://www.dailypay.com/help/
- type: Blog
  url: https://www.dailypay.com/resource-center/blog/
- type: BlogRSS
  url: https://www.dailypay.com/resource-center/blog/feed/
- type: GitHubOrganization
  url: https://github.com/dailypay
- type: SignUp
  url: https://dailypay.app.link/vYyj0iSlyTb
- type: Login
  url: https://account.dailypay.com/
- type: TermsOfService
  url: https://www.dailypay.com/en-us/legal/terms-of-service/
- type: PrivacyPolicy
  url: https://www.dailypay.com/en-us/legal/privacy/
- type: Compliance
  url: https://www.dailypay.com/en-us/legal/compliance/
- type: TrustCenter
  url: security/dailypay-trust-center.yml
- type: Security
  url: https://www.dailypay.com/security/vulnerability-disclosure-program/
- type: VulnerabilityDisclosure
  url: security/dailypay-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/dailypay-domain-security.yml
- type: StatusPage
  url: https://status.dailypay.com/
- type: Lifecycle
  url: lifecycle/dailypay-lifecycle.yml
- type: Packages
  url: packages/dailypay-packages.yml
- type: SDKs
  url: packages/dailypay-packages.yml
- type: Conventions
  url: conventions/dailypay-conventions.yml
- type: Idempotency
  url: conventions/dailypay-conventions.yml
- type: ErrorCatalog
  url: errors/dailypay-problem-types.yml
- type: DeclineCodes
  url: errors/dailypay-decline-codes.yml
- type: DataModel
  url: data-model/dailypay-data-model.yml
- type: Conformance
  url: conformance/dailypay-conformance.yml
- type: Sandbox
  url: sandbox/dailypay-sandbox.yml
- type: Components
  url: components/dailypay-components.yml
- type: WellKnown
  url: well-known/dailypay-well-known.yml
- type: MCPServer
  url: mcp/dailypay-mcp.yml
- type: ToolCrosswalk
  url: mcp/dailypay-tool-crosswalk.yml
- type: LLMsTxt
  url: llms/dailypay-llms.txt
- type: AgenticAccess
  url: agentic-access/dailypay-agentic-access.yml
- type: AgentSkill
  url: skills/_index.yml

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/dailypay"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/dailypay/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/dailypay/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.