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.

58.2/100 strong Agent 54/100 agent native Full breakdown ↓
scored 2026-08-03 · rubric v0.9
1 APIs 1 MCP Servers
CompanyPaymentsPayrollHuman ResourcesEarned Wage AccessOn-Demand PayFinancial ServicesFintechMoney TransferBenefits

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-03 · rubric v0.9
Composite quality — 58.2/100 · strong
Contract Quality 15.4 / 25
Developer Ergonomics 15.1 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 4.1 / 13
Governance 2.5 / 12
Discoverability 8.7 / 10
Agent readiness — 54/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
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 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
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.

dailypay-mcp.yml

MCP SERVER

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Dailypay Authentication

oauth2/openIdConnect · 2 schemes

SECURITY

Dailypay Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Dailypay Vulnerability Disclosure

Hackerone · security.txt

SECURITY

Dailypay Trust Center

SOC 2, ISO 27001, PCI DSS

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Dailypay Scopes

5 scopes · clientCredentials/authorizationCode

5 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Dailypay Agentic Access

18 operations · 6 acting

18 operations · 6 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 5

SDKs, sample code, and the tooling you integrate with

Access & Security 7

Authentication, authorization, and security posture

Scroll for all 7

Operate 3

Status, limits, changes, and where to get help

Commercial 2

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

Source (apis.yml)

apis.yml Raw ↑
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.20'
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
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:
  - 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
Where this information came from

This is an independent, third-party profile of DailyPay, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.