PlanSource

PlanSource is a benefits administration and employee-benefits engagement platform used by employers, brokers, carriers and HR/payroll partners to run enrollment, eligibility, billing and benefits communication. Its public developer surface is the PlanSource Benefits Administration API (Admin API v2), a RESTful HTTPS API of 80 operations across 62 paths covering employee (subscriber) demographics, dependents, beneficiaries, coverages and stacked coverage lines, payroll deductions with lookup codes and pre-tax/post-tax/employer/imputed amounts, Evidence of Insurability decisions and form completions, ACA offer and enrollee reporting data, administrator accounts, and organization portal page content. It is designed to replace fixed-schedule EDI files with near real-time sync between an HCM/payroll system of record and PlanSource. Authentication is OAuth 2.0 client credentials (scope admin_api_v2) or a legacy AuthenticationString + Signature header pair, with OpenID Connect and SAML 2.0 available for end-user single sign-on. The API is documented on a ReadMe developer portal that publishes llms.txt, an agent-skills manifest and an OAuth-gated MCP server, and PlanSource maintains a SafeBase trust center listing SOC 2 Type 2, ISO/IEC 27001:2022, HIPAA, CCPA and 23 NYCRR 500.

PlanSource publishes 9 API contracts indexed on the APIs.io network, including ACA API, Administrators API, Collections API, and 6 more. Tagged areas include Employee Benefits, Benefits Administration, Insurance, Human Resources, and Payroll.

The PlanSource catalog on APIs.io includes 1 Spectral governance ruleset.

PlanSource’s developer surface includes engineering blog, documentation, API reference, getting-started guide, support, authentication, sandbox, and 25 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

48.7/100 developing ▬ flat Agent 46/100 agent ready Front door AI 3/6 light Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 1 MCP Servers 4 Agent Skills

Employee Benefits Benefits Administration Insurance Human Resources Payroll Health Insurance Enrollment HR Technology Evidence of InsurabilityACA ReportingEligibility SSO Identity Federation

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Human Capital Management

BC-300

ACACoverageDemographicEOIPayroll

POST /coverage PUT /coverage/subscriber/{subscriber_id}/terminate POST /coverage/{coverage_id}/line GET /eoi/subscriber/{subscriber_id}

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 48.7/100 · developing

Contract Quality 10.7 / 19

Developer Ergonomics 8.7 / 15

Access Clarity 6.5 / 15

Operational Transparency 0.0 / 10

Contract Governance 2.9 / 9

Discoverability 5.6 / 8

Regulatory Posture 6.2 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 46/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 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

Delegated User Identity 0 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Insurance 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.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

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

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/plansource/"><img src="https://apis.io/badge/plansource/card.svg" alt="PlanSource on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Operational Transparency scores 0.0 — up to +13.0 composite points
Access Clarity scores 43.4 — up to +11.3 composite points
Contract Quality scores 56.9 — up to +10.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/plansource/apis.yml: open an issue on github.com/api-evangelist/plansource to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
HCM and Payroll Marketplaces (ADP, Workday, UKG, Paylocity)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 6

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

SSO

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

OpenID Connect

measured — observed by APIs.io (declared)

APIs 9

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

PlanSource ACA API

Affordable Care Act data.

PlanSource Administrators API

Administrator Management

PlanSource Collections API

Collections of objects.

PlanSource Coverage API

Coverages, coverage lines, and dependent coverages.

PlanSource Demographic API

Subscribers, their dependents and beneficiaries.

PlanSource EOI API

Evidence of Insurability Processing.

PlanSource Page Content API

Organization page content data.

PlanSource Payroll API

Payroll coverages data.

PlanSource Security API

Security Functions

Scroll for all 9

Open Collections 13

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Plansource Admin ACA API

OPEN COLLECTION

Plansource Admin Administrators API

OPEN COLLECTION

Plansource Admin All API

OPEN COLLECTION

Plansource Admin Collections API

OPEN COLLECTION

Plansource Admin Composites API

OPEN COLLECTION

Plansource Admin Coverage API

OPEN COLLECTION

Plansource Admin Demographic API

OPEN COLLECTION

Plansource Admin EOI API

OPEN COLLECTION

Plansource Admin Page Content API

OPEN COLLECTION

Plansource Admin Payroll API

OPEN COLLECTION

Plansource Admin Processing API

OPEN COLLECTION

Plansource Admin Resources API

OPEN COLLECTION

Plansource Admin Security API

OPEN COLLECTION

Scroll for all 13

MCP Servers 1

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

PlanSource MCP Server

Remote MCP server at developer.plansource.com over HTTP.

MCP SERVER

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

Create, stack, and terminate benefit coverages

AGENT SKILL

Return carrier EOI decisions to PlanSource

AGENT SKILL

Pull payroll deductions back into the payroll system

AGENT SKILL

Sync employee demographics from an HCM into PlanSource

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

PlanSource API Rules

69 rules · 54 errors 13 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Plansource Admin Api Overlay

5 actions · update · plansource-admin-api-openapi-original.json

DERIVED

Security Posture 3

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

Plansource Authentication

oauth2/apiKey/openIdConnect/saml2 · 5 schemes

SECURITY

Plansource Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Plansource Trust Center

SOC 2 Type 2, ISO/IEC 27001:2022, HIPAA, CCPA, 23 NYCRR 500

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Plansource Scopes

8 scopes · clientCredentials/authorizationCode

8 scopes

SCOPES

Agentic Access 1

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

Plansource Agentic Access

80 operations · 44 acting · 10 human-in-the-loop

80 operations · 44 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

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

LLMsTxt

WellKnown

MCPServer

AgentSkill

AgenticAccess

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

Lifecycle

Conventions

ErrorCatalog

DataModel

Build 2

SDKs, sample code, and the tooling you integrate with

Postman

Postman

Examples

Examples

Access & Security 5

Authentication, authorization, and security posture

TrustCenter

Compliance

DomainSecurity

Authentication

OAuthScopes

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

Blog

BlogRSS

Website

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: plansource
name: PlanSource
description: PlanSource is a benefits administration and employee-benefits engagement platform used by employers, brokers,
  carriers and HR/payroll partners to run enrollment, eligibility, billing and benefits communication. Its public developer
  surface is the PlanSource Benefits Administration API (Admin API v2), a RESTful HTTPS API of 80 operations across 62 paths
  covering employee (subscriber) demographics, dependents, beneficiaries, coverages and stacked coverage lines, payroll deductions
  with lookup codes and pre-tax/post-tax/employer/imputed amounts, Evidence of Insurability decisions and form completions,
  ACA offer and enrollee reporting data, administrator accounts, and organization portal page content. It is designed to replace
  fixed-schedule EDI files with near real-time sync between an HCM/payroll system of record and PlanSource. Authentication
  is OAuth 2.0 client credentials (scope admin_api_v2) or a legacy AuthenticationString + Signature header pair, with OpenID
  Connect and SAML 2.0 available for end-user single sign-on. The API is documented on a ReadMe developer portal that publishes
  llms.txt, an agent-skills manifest and an OAuth-gated MCP server, and PlanSource maintains a SafeBase trust center listing
  SOC 2 Type 2, ISO/IEC 27001:2022, HIPAA, CCPA and 23 NYCRR 500.
url: https://raw.githubusercontent.com/api-evangelist/plansource/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://plansource.com/wp-content/uploads/2026/01/ps_social-share-img.webp
x-type: company
x-source: harvest:insurance-benefits-admin
specificationVersion: '0.23'
created: '2026-08-06'
modified: '2026-10-06'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Employee Benefits
- Benefits Administration
- Insurance
- Human Resources
- Payroll
- Health Insurance
- Enrollment
- HR Technology
- Evidence of Insurability
- ACA Reporting
- Eligibility
- SSO
- Identity Federation
tags_raw:
- Employee Benefits
- Benefits Administration
- Insurance
- Human Resources
- Payroll
- Health Insurance
- Enrollment
- HR Technology
- Evidence of Insurability
- ACA Reporting
- Eligibility
- Single Sign-On
- Identity Federation
apis:
- aid: plansource:plansource-aca-api
  name: PlanSource ACA API
  description: Affordable Care Act data.
  humanURL: https://developer.plansource.com/v2.0/reference
  baseURL: https://api.plansource.com/admin/v2
  tags:
  - ACA
  properties:
  - type: OpenAPI
    url: openapi/plansource-aca-api-openapi.yml
  - type: Examples
    url: examples/plansource-examples.yml
  - type: Authentication
    url: authentication/plansource-authentication.yml
  - type: OAuthScopes
    url: scopes/plansource-scopes.yml
  - type: ErrorCatalog
    url: errors/plansource-problem-types.yml
  - type: Conventions
    url: conventions/plansource-conventions.yml
  - type: DataModel
    url: data-model/plansource-data-model.yml
  - type: Lifecycle
    url: lifecycle/plansource-lifecycle.yml
  - type: Sandbox
    url: sandbox/plansource-sandbox.yml
  - type: Conformance
    url: conformance/plansource-conformance.yml
  - type: AgenticAccess
    url: agentic-access/plansource-agentic-access.yml
  - type: ToolCrosswalk
    url: mcp/plansource-tool-crosswalk.yml
  - type: Postman
    url: https://www.getpostman.com/collections/93f063e64815e4122102
  - type: APIReference
    url: https://developer.plansource.com/v2.0/reference
  - type: Documentation
    url: https://developer.plansource.com/docs/plansource-administrative-api
- aid: plansource:plansource-administrators-api
  name: PlanSource Administrators API
  description: Administrator Management
  humanURL: https://developer.plansource.com/v2.0/reference
  baseURL: https://api.plansource.com/admin/v2
  tags:
  - Administrators
  properties:
  - type: OpenAPI
    url: openapi/plansource-administrators-api-openapi.yml
  - type: Examples
    url: examples/plansource-examples.yml
  - type: Authentication
    url: authentication/plansource-authentication.yml
  - type: OAuthScopes
    url: scopes/plansource-scopes.yml
  - type: ErrorCatalog
    url: errors/plansource-problem-types.yml
  - type: Conventions
    url: conventions/plansource-conventions.yml
  - type: DataModel
    url: data-model/plansource-data-model.yml
  - type: Lifecycle
    url: lifecycle/plansource-lifecycle.yml
  - type: Sandbox
    url: sandbox/plansource-sandbox.yml
  - type: Conformance
    url: conformance/plansource-conformance.yml
  - type: AgenticAccess
    url: agentic-access/plansource-agentic-access.yml
  - type: ToolCrosswalk
    url: mcp/plansource-tool-crosswalk.yml
  - type: Postman
    url: https://www.getpostman.com/collections/93f063e64815e4122102
  - type: APIReference
    url: https://developer.plansource.com/v2.0/reference
  - type: Documentation
    url: https://developer.plansource.com/docs/plansource-administrative-api
- aid: plansource:plansource-collections-api
  name: PlanSource Collections API
  description: Collections of objects.
  humanURL: https://developer.plansource.com/v2.0/reference
  baseURL: https://api.plansource.com/admin/v2
  tags:
  - Collection
  tags_raw:
  - Collections
  properties:
  - type: OpenAPI
    url: openapi/plansource-collections-api-openapi.yml
  - type: Examples
    url: examples/plansource-examples.yml
  - type: Authentication
    url: authentication/plansource-authentication.yml
  - type: OAuthScopes
    url: scopes/plansource-scopes.yml
  - type: ErrorCatalog
    url: errors/plansource-problem-types.yml
  - type: Conventions
    url: conventions/plansource-conventions.yml
  - type: DataModel
    url: data-model/plansource-data-model.yml
  - type: Lifecycle
    url: lifecycle/plansource-lifecycle.yml
  - type: Sandbox
    url: sandbox/plansource-sandbox.yml
  - type: Conformance
    url: conformance/plansource-conformance.yml
  - type: AgenticAccess
    url: agentic-access/plansource-agentic-access.yml
  - type: ToolCrosswalk
    url: mcp/plansource-tool-crosswalk.yml
  - type: Postman
    url: https://www.getpostman.com/collections/93f063e64815e4122102
  - type: APIReference
    url: https://developer.plansource.com/v2.0/reference
  - type: Documentation
    url: https://developer.plansource.com/docs/plansource-administrative-api
- aid: plansource:plansource-coverage-api
  name: PlanSource Coverage API
  description: Coverages, coverage lines, and dependent coverages.
  humanURL: https://developer.plansource.com/v2.0/reference
  baseURL: https://api.plansource.com/admin/v2
  tags:
  - Coverage
  properties:
  - type: OpenAPI
    url: openapi/plansource-coverage-api-openapi.yml
  - type: Examples
    url: examples/plansource-examples.yml
  - type: Authentication
    url: authentication/plansource-authentication.yml
  - type: OAuthScopes
    url: scopes/plansource-scopes.yml
  - type: ErrorCatalog
    url: errors/plansource-problem-types.yml
  - type: Conventions
    url: conventions/plansource-conventions.yml
  - type: DataModel
    url: data-model/plansource-data-model.yml
  - type: Lifecycle
    url: lifecycle/plansource-lifecycle.yml
  - type: Sandbox
    url: sandbox/plansource-sandbox.yml
  - type: Conformance
    url: conformance/plansource-conformance.yml
  - type: AgenticAccess
    url: agentic-access/plansource-agentic-access.yml
  - type: ToolCrosswalk
    url: mcp/plansource-tool-crosswalk.yml
  - type: Postman
    url: https://www.getpostman.com/collections/93f063e64815e4122102
  - type: APIReference
    url: https://developer.plansource.com/v2.0/reference
  - type: Documentation
    url: https://developer.plansource.com/docs/plansource-administrative-api
- aid: plansource:plansource-demographic-api
  name: PlanSource Demographic API
  description: Subscribers, their dependents and beneficiaries.
  humanURL: https://developer.plansource.com/v2.0/reference
  baseURL: https://api.plansource.com/admin/v2
  tags:
  - Demographic
  properties:
  - type: OpenAPI
    url: openapi/plansource-demographic-api-openapi.yml
  - type: Examples
    url: examples/plansource-examples.yml
  - type: Authentication
    url: authentication/plansource-authentication.yml
  - type: OAuthScopes
    url: scopes/plansource-scopes.yml
  - type: ErrorCatalog
    url: errors/plansource-problem-types.yml
  - type: Conventions
    url: conventions/plansource-conventions.yml
  - type: DataModel
    url: data-model/plansource-data-model.yml
  - type: Lifecycle
    url: lifecycle/plansource-lifecycle.yml
  - type: Sandbox
    url: sandbox/plansource-sandbox.yml
  - type: Conformance
    url: conformance/plansource-conformance.yml
  - type: AgenticAccess
    url: agentic-access/plansource-agentic-access.yml
  - type: ToolCrosswalk
    url: mcp/plansource-tool-crosswalk.yml
  - type: Postman
    url: https://www.getpostman.com/collections/93f063e64815e4122102
  - type: APIReference
    url: https://developer.plansource.com/v2.0/reference
  - type: Documentation
    url: https://developer.plansource.com/docs/plansource-administrative-api
- aid: plansource:plansource-eoi-api
  name: PlanSource EOI API
  description: Evidence of Insurability Processing.
  humanURL: https://developer.plansource.com/v2.0/reference
  baseURL: https://api.plansource.com/admin/v2
  tags:
  - EOI
  properties:
  - type: OpenAPI
    url: openapi/plansource-eoi-api-openapi.yml
  - type: Examples
    url: examples/plansource-examples.yml
  - type: Authentication
    url: authentication/plansource-authentication.yml
  - type: OAuthScopes
    url: scopes/plansource-scopes.yml
  - type: ErrorCatalog
    url: errors/plansource-problem-types.yml
  - type: Conventions
    url: conventions/plansource-conventions.yml
  - type: DataModel
    url: data-model/plansource-data-model.yml
  - type: Lifecycle
    url: lifecycle/plansource-lifecycle.yml
  - type: Sandbox
    url: sandbox/plansource-sandbox.yml
  - type: Conformance
    url: conformance/plansource-conformance.yml
  - type: AgenticAccess
    url: agentic-access/plansource-agentic-access.yml
  - type: ToolCrosswalk
    url: mcp/plansource-tool-crosswalk.yml
  - type: Postman
    url: https://www.getpostman.com/collections/93f063e64815e4122102
  - type: APIReference
    url: https://developer.plansource.com/v2.0/reference
  - type: Documentation
    url: https://developer.plansource.com/docs/plansource-administrative-api
- aid: plansource:plansource-page-content-api
  name: PlanSource Page Content API
  description: Organization page content data.
  humanURL: https://developer.plansource.com/v2.0/reference
  baseURL: https://api.plansource.com/admin/v2
  tags:
  - Page content
  tags_raw:
  - Page Content
  properties:
  - type: OpenAPI
    url: openapi/plansource-page-content-api-openapi.yml
  - type: Examples
    url: examples/plansource-examples.yml
  - type: Authentication
    url: authentication/plansource-authentication.yml
  - type: OAuthScopes
    url: scopes/plansource-scopes.yml
  - type: ErrorCatalog
    url: errors/plansource-problem-types.yml
  - type: Conventions
    url: conventions/plansource-conventions.yml
  - type: DataModel
    url: data-model/plansource-data-model.yml
  - type: Lifecycle
    url: lifecycle/plansource-lifecycle.yml
  - type: Sandbox
    url: sandbox/plansource-sandbox.yml
  - type: Conformance
    url: conformance/plansource-conformance.yml
  - type: AgenticAccess
    url: agentic-access/plansource-agentic-access.yml
  - type: ToolCrosswalk
    url: mcp/plansource-tool-crosswalk.yml
  - type: Postman
    url: https://www.getpostman.com/collections/93f063e64815e4122102
  - type: APIReference
    url: https://developer.plansource.com/v2.0/reference
  - type: Documentation
    url: https://developer.plansource.com/docs/plansource-administrative-api
- aid: plansource:plansource-payroll-api
  name: PlanSource Payroll API
  description: Payroll coverages data.
  humanURL: https://developer.plansource.com/v2.0/reference
  baseURL: https://api.plansource.com/admin/v2
  tags:
  - Payroll
  properties:
  - type: OpenAPI
    url: openapi/plansource-payroll-api-openapi.yml
  - type: Examples
    url: examples/plansource-examples.yml
  - type: Authentication
    url: authentication/plansource-authentication.yml
  - type: OAuthScopes
    url: scopes/plansource-scopes.yml
  - type: ErrorCatalog
    url: errors/plansource-problem-types.yml
  - type: Conventions
    url: conventions/plansource-conventions.yml
  - type: DataModel
    url: data-model/plansource-data-model.yml
  - type: Lifecycle
    url: lifecycle/plansource-lifecycle.yml
  - type: Sandbox
    url: sandbox/plansource-sandbox.yml
  - type: Conformance
    url: conformance/plansource-conformance.yml
  - type: AgenticAccess
    url: agentic-access/plansource-agentic-access.yml
  - type: ToolCrosswalk
    url: mcp/plansource-tool-crosswalk.yml
  - type: Postman
    url: https://www.getpostman.com/collections/93f063e64815e4122102
  - type: APIReference
    url: https://developer.plansource.com/v2.0/reference
  - type: Documentation
    url: https://developer.plansource.com/docs/plansource-administrative-api
- aid: plansource:plansource-security-api
  name: PlanSource Security API
  description: Security Functions
  humanURL: https://developer.plansource.com/v2.0/reference
  baseURL: https://api.plansource.com/admin/v2
  tags:
  - Security
  properties:
  - type: OpenAPI
    url: openapi/plansource-security-api-openapi.yml
  - type: Examples
    url: examples/plansource-examples.yml
  - type: Authentication
    url: authentication/plansource-authentication.yml
  - type: OAuthScopes
    url: scopes/plansource-scopes.yml
  - type: ErrorCatalog
    url: errors/plansource-problem-types.yml
  - type: Conventions
    url: conventions/plansource-conventions.yml
  - type: DataModel
    url: data-model/plansource-data-model.yml
  - type: Lifecycle
    url: lifecycle/plansource-lifecycle.yml
  - type: Sandbox
    url: sandbox/plansource-sandbox.yml
  - type: Conformance
    url: conformance/plansource-conformance.yml
  - type: AgenticAccess
    url: agentic-access/plansource-agentic-access.yml
  - type: ToolCrosswalk
    url: mcp/plansource-tool-crosswalk.yml
  - type: Postman
    url: https://www.getpostman.com/collections/93f063e64815e4122102
  - type: APIReference
    url: https://developer.plansource.com/v2.0/reference
  - type: Documentation
    url: https://developer.plansource.com/docs/plansource-administrative-api
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://plansource.com/news/
  type: Blog
- url: https://plansource.com/feed/
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/plansource-capability-edges.yml
  name: PlanSource Business Capability Map
- type: Overlay
  url: overlays/plansource-admin-api-overlay.yaml
- type: Website
  url: https://plansource.com/
- type: DeveloperPortal
  url: https://developer.plansource.com/
- type: Documentation
  url: https://developer.plansource.com/docs/plansource-administrative-api
- type: APIReference
  url: https://developer.plansource.com/v2.0/reference
- type: GettingStarted
  url: https://developer.plansource.com/docs/utilize-postman
- type: Postman
  url: https://www.getpostman.com/collections/93f063e64815e4122102
- type: Support
  url: https://developer.plansource.com/docs/contact-support
- type: Blog
  url: https://plansource.com/blog/
- type: Login
  url: https://benefits.plansource.com/
- type: TermsOfService
  url: https://plansource.com/terms-of-use/
- type: PrivacyPolicy
  url: https://plansource.com/privacy/
- type: TrustCenter
  url: security/plansource-trust-center.yml
- type: Compliance
  url: https://trust.plansource.com/
- type: LLMsTxt
  url: llms/plansource-llms.txt
- type: WellKnown
  url: well-known/plansource-well-known.yml
- type: MCPServer
  url: mcp/plansource-mcp.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/plansource-domain-security.yml
- type: Authentication
  url: authentication/plansource-authentication.yml
- type: OAuthScopes
  url: scopes/plansource-scopes.yml
- type: Conformance
  url: conformance/plansource-conformance.yml
- type: Lifecycle
  url: lifecycle/plansource-lifecycle.yml
- type: Sandbox
  url: sandbox/plansource-sandbox.yml
- type: Conventions
  url: conventions/plansource-conventions.yml
- type: ErrorCatalog
  url: errors/plansource-problem-types.yml
- type: DataModel
  url: data-model/plansource-data-model.yml
- type: Examples
  url: examples/plansource-examples.yml
- type: AgenticAccess
  url: agentic-access/plansource-agentic-access.yml
x-enrichment:
  date: '2026-08-06'
  status: enriched
  artifacts_added: 27
  pass: local-v1

PlanSource API — frequently asked questions

Does PlanSource have an API?

Yes. APIs.io lists 9 APIs from PlanSource, including PlanSource ACA API, PlanSource Administrators API and PlanSource Collections API, and 6 more.

Is there an OpenAPI specification for the PlanSource API?

Yes. APIs.io indexes 9 OpenAPI specifications for PlanSource, each linked for download from this page.

How do I authenticate with the PlanSource API?

PlanSource documents its authentication (oauth2/apiKey/openIdConnect/saml2 · 5 schemes). The details are profiled on APIs.io as Plansource Authentication.

Does PlanSource have an MCP server?

Yes. APIs.io lists 1 MCP server for PlanSource: Remote MCP server at developer.plansource.com over HTTP.

Is the PlanSource API ready for AI agents?

PlanSource has a Kin Score of 48.7 out of 100 (developing) and an Agent Readiness score of 46.4 (agent-ready), scored by API Evangelist on 2026-11-06.

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/plansource"

All providers

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

Every operation they expose

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

How their score was established

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

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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