$HEADLESS SYSTEMS
03 / Scorecard / Auth & Identity

PropelAuth

B
Headless Index
60/100
JAIRF
N/A
Verified
AUG 20, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

PropelAuth earns Band B in the Auth & Identity category of The Headless Index, with a thesis-fit score of 60/100. Its strongest dimension is API-first design intent (16/20); its weakest scored dimension is MCP and agent posture (4/20). No public OpenAPI specification was found when PropelAuth was scored, which limits how far an agent can go without human integration work.

Editorial verdict
PropelAuth is solidly built for programmatic consumption. The Headless Index thesis-fit score of 60/100 lands it in the upper-middle of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where PropelAuth lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. PropelAuth is a B2B SaaS identity product with a REST Management API plus SDKs in Node, Python, Go, Java, and PHP. The API covers organisations, users, roles, custom properties, audit logs, and SSO configuration. Product positioning is explicitly B2B multi-tenant, which shapes the API around organisation primitives.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documentation is detailed at docs.propelauth.com. A public OpenAPI URL is not prominently exposed, but the SDK code generation pattern suggests one exists internally.[2] An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Organisation CRUD, user provisioning, role and permission authoring, SSO configuration, magic-link delivery, and audit log access are all programmable. The PropelAuth dashboard is the self-service surface; the API does everything the dashboard does.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party PropelAuth MCP server is published. The B2B SaaS positioning leaves the agent-protocol layer to downstream framework wrappers.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Webhooks for organisation lifecycle, user events, and role changes are documented with HMAC signing. The catalog is appropriately scoped for B2B SaaS multi-tenant identity. Net assessment: PropelAuth can be operated by agents for the majority of practical workflows. The closest thing to a gap is MCP posture[5], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent16/20
scored

PropelAuth is a B2B SaaS identity product with a REST Management API plus SDKs in Node, Python, Go, Java, and PHP. The API covers organisations, users, roles, custom properties, audit logs, and SSO configuration. Product positioning is explicitly B2B multi-tenant, which shapes the API around organisation primitives.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −OpenAPI specNot found across 34 probe paths
  • −GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
  • ·SDKs maintained2 (go, python); top by stars: PropelAuth/propelauth-py (13 stars)
cite (1)
  • github.sdks@2026-05-19
Headless operation14/20
scored

Organisation CRUD, user provisioning, role and permission authoring, SSO configuration, magic-link delivery, and audit log access are all programmable. The PropelAuth dashboard is the self-service surface; the API does everything the dashboard does.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −API operations exposedNo OpenAPI spec; operations count unknown
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (1)
  • github.sdks@2026-05-19
MCP & agent posture4/20
scored

No first-party PropelAuth MCP server is published. The B2B SaaS positioning leaves the agent-protocol layer to downstream framework wrappers.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −Official MCP serverNone found in vendor's GitHub org or the official MCP registry
  • −Community MCP serversNone found
  • −Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)
cite (1)
  • github.sdks@2026-05-19
Schema observability14/20
scored

REST documentation is detailed at docs.propelauth.com. A public OpenAPI URL is not prominently exposed, but the SDK code generation pattern suggests one exists internally.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −OpenAPINot discovered across 34 standard probe paths
  • −GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)
cite (1)
  • github.sdks@2026-05-19
Webhooks & events12/20
scored

Webhooks for organisation lifecycle, user events, and role changes are documented with HMAC signing. The catalog is appropriately scoped for B2B SaaS multi-tenant identity.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • github.sdks@2026-05-19
JAIRF · 6 dimensions
JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Powered by JAIRF v1.0.0 by Jentic

Band rationale:B band: JAIRF=N/A HeadlessIndex=60

04 / Embed

Show PropelAuth's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

PropelAuth mini badge preview
Get embed code
Peers in Auth & Identity
UnkeyB
Headless Index 60/100
KindeC
Headless Index 58/100
Better AuthB
Headless Index 63/100
See full Auth & Identity ranking →
FAQ

PropelAuth and agent readiness

Is PropelAuth agent-ready?
PropelAuth scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.
Does PropelAuth publish an OpenAPI spec?
No published OpenAPI specification was found when PropelAuth was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is PropelAuth's Headless Index score?
PropelAuth scores 60/100 on the Headless Index thesis-fit rubric and sits in Band B in the Auth & Identity category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.