Permit.io
Permit.io is an authorization-as-a-service platform that helps developers build, manage, and enforce fine-grained access control in their applications. It provides a Policy Decision Point (PDP), management API, REST API, and permission query APIs for role-based, attribute-based, and relationship-based access control with support for bulk checks, data filtering, and URL-based enforcement.
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 Permit.io the way a machine reads it — 52 machine-readable artifacts across 43 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 — Permit.io scores 48.0/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Permit.io
Each block below is one kind of artifact we hold for Permit.io. 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 43
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.
Permit.io Activity Log API
The Activity Log API from Permit.io — 2 operation(s) for activity log.
Permit.io API History API
The API History API from Permit.io — 4 operation(s) for api history.
Permit.io API Keys API
The API Keys API from Permit.io — 5 operation(s) for api keys.
Permit.io Audit Elements Data API
The Audit Elements Data API from Permit.io — 1 operation(s) for audit elements data.
Permit.io Audit Log Replay API
The Audit Log Replay API from Permit.io — 1 operation(s) for audit log replay.
Permit.io Audit Logs API
The Audit Logs API from Permit.io — 2 operation(s) for audit logs.
Permit.io Condition Set Rules API
Represents a "mini" ABAC rule comprised of (UserSet, Action, ResourceSet). If such tuple exists, it means all users matching the UserSet can perform the Action on the resources ...
Permit.io Condition Sets API
Condition sets are sets of objects that are dynamically defined based on conditions on the objects' attributes. Conditions sets allows you the flexibility of ABAC with the simpl...
Permit.io Deprecated API
The Deprecated API from Permit.io — 6 operation(s) for deprecated.
Permit.io Elements Configs (EAP) API
The Elements Configs (EAP) API from Permit.io — 4 operation(s) for elements configs (eap).
Permit.io Environments API
Environments are silos contained within projects that enables you to safely iterate on changes. Environments allow you to manage your policy throughout your entire development l...
Permit.io Groups API
The Groups API from Permit.io — 10 operation(s) for groups.
Permit.io Implicit Grants API
The Implicit Grants API from Permit.io — 2 operation(s) for implicit grants.
Permit.io Invites API
The Invites API from Permit.io — 2 operation(s) for invites.
Permit.io Members API
The Members API from Permit.io — 3 operation(s) for members.
Permit.io OPAL Data ( EAP ) API
The OPAL Data ( EAP ) API from Permit.io — 6 operation(s) for opal data ( eap ).
Permit.io Operation Approval (EAP) API
The Operation Approval (EAP) API from Permit.io — 6 operation(s) for operation approval (eap).
Permit.io Organizations API
The Organizations API gives you access to control and manage your Permit organizations. An organization represents a **single billable account** (i.e: a company using Permit). Y...
Permit.io Policy Decision Points API
The Policy Decision Points API from Permit.io — 6 operation(s) for policy decision points.
Permit.io Policy Git Repositories API
The Policy Git Repositories API from Permit.io — 5 operation(s) for policy git repositories.
Permit.io Policy Guards (EAP) API
The Policy Guards (EAP) API from Permit.io — 5 operation(s) for policy guards (eap).
Permit.io Projects API
Projects let you manage permissions for different business objectives from a single Permit account. For example, you can create one project called "Billing App" and another proj...
Permit.io Proxy Config API
Proxy Config is set to enable the Permit Proxy to make proxied requests as part of the Frontend AuthZ.
Permit.io Relationship tuples API
The Relationship tuples API from Permit.io — 3 operation(s) for relationship tuples.
Permit.io Resource Action Groups API
Resource Action Groups are groups of actions that are assigned to a role as one action.
Permit.io Resource Actions API
Actions are the various ways you can interact with a resource or affect the resource. Each (resource, action) pair defines a unique permission level.
Permit.io Resource Attributes API
Resource attributes allow you to specify an arbitrary schema attributes that are part of the definition of resource and must be included in any of its instances. Attributes are ...
Permit.io Resource Instances API
Resource instances are instances of resource types. An instance represents **a single object** in your system on which you'd want to enforce authorization. You can use this API ...
Permit.io Resource Relations API
The Resource Relations API from Permit.io — 2 operation(s) for resource relations.
Permit.io Resource Roles API
Roles allow you to associate permissions indirectly via a job function. Resource roles allow you to grant roles that are scoped to a resource, thus expressing ownership or arbit...
Permit.io Resources API
Resources are *types* of objects or feature names that you wish to protect (or gate) with permissions. For example, if you build a document-sharing app like google docs, you mig...
Permit.io Role Assignments API
Role Assignments are RBAC-constructs that state that a actor (i.e: user) is assigned a role within a tenant. With role assignments you can assign or unassign roles to a user. Ro...
Permit.io Roles API
Roles allow you to associate permissions indirectly via a job function. The Roles API allows you to manipulate roles: assign or unassign permissions to a role, define hierarchy ...
Permit.io Scope Configurations API
The Scope Configurations API from Permit.io — 1 operation(s) for scope configurations.
Permit.io Tenants API
A tenant is a group of users that share a common organizational identity. Each tenant is a silo that can enforce strict boundaries between your customers. You can associate your...
Permit.io User Attributes API
User attributes allow you to specify an arbitrary schema attributes that are part of the definition of the User resource. Attributes are used to enforce attribute-based access c...
Permit.io User Invites API
The User Invites API from Permit.io — 3 operation(s) for user invites.
Permit.io Users API
Users represent human end-users of your applications that you'd like to enforce permissions on. You must create a user object in Permit.io prior to trying to enforce permissions...
Permit.io Users Elements Data API
The Users Elements Data API from Permit.io — 6 operation(s) for users elements data.
Scroll within the panel for all 43 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Permit.io API
OPEN COLLECTIONPricing 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.
Rate 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.
Permit Io 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.
Permit Io Finops
FINOPSSecurity Posture 4
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 Permit.io — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
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 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/permit-io · machine-readable index on apis.io