Know of an official OpenAPI document? Contribute it →
For Agents
Generate test identities with PhantAuth: register test clients, create and read generated users, request user tokens, and read domains, tenants, teams, and fleets.
Use for: Register a test client, Create a random test user, Look up a generated user, Get a token for a test user
Not supported: Generates disposable test users, clients, tokens, and grouping data for exercising authentication flows. Does not manage real user accounts, secure production sign-in, or store real personal data.
PhantAuth is a random user generator and OpenID Connect provider built for testing, described by its authors as Lorem Ipsum for user accounts and authentication. Through its REST endpoints you register test clients, create and read generated users, request tokens for a user, and read grouping resources such as domains, tenants, teams, and fleets. Because the users and tokens are generated on demand, teams use it to exercise sign-in flows and OpenID Connect integrations without standing up a real identity provider or handling real personal data.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PhantAuth, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fphantauth.net%2Fphantauth" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fphantauth.net%2Fphantauth" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with PhantAuth API.
Register a test client for an OpenID Connect flow
Read a registered test client by its identifier
Create a generated test user
Read a generated user by username
Request a token for a user for a given kind
Read grouping resources: domains, tenants, teams, and fleets
Patterns agents use PhantAuth API for, with concrete tasks.
★ Exercise a sign-in flow with generated users
Test an application's login without a real identity provider. The agent creates generated users and reads them back, so a sign-in flow can be driven end to end against disposable accounts instead of real ones.
Create a generated test user and read it back so a sign-in flow can be exercised against a disposable account.
Register clients for OIDC integration tests
Set up the client side of an OpenID Connect test. The agent registers a test client and reads it back, so an integration test has a client to run authorisation flows against.
Register a test client and read it back so an OpenID Connect integration test has a client to use.
Mint tokens for test scenarios
Get tokens for generated users to drive downstream tests. The agent requests a token of the required kind for a user, so a test can present it to an application expecting an OpenID Connect token.
Request a token of the required kind for a generated user so a downstream test can use it.
Model grouping structures in tests
Represent organisational structure in a test environment. The agent reads generated domains, tenants, teams, and fleets so a multi-tenant application can be tested against realistic-looking groupings without real data.
Read the generated domain, tenant, team, or fleet so a multi-tenant test has grouping data to work with.
10 endpoints — phantauth is a random user generator and openid connect provider built for testing, described by its authors as lorem ipsum for user accounts and authentication.
METHOD
PATH
DESCRIPTION
/client
Register a test client
/client/{client_id}
Read a registered test client
/user
Create a generated test user
/user/{username}
Read a generated user
/user/{username}/token/{kind}
Request a token for a user
/client
Register a test client
/client/{client_id}
Read a registered test client
/user
Create a generated test user
/user/{username}
Read a generated user
/user/{username}/token/{kind}
Request a token for a user
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Using PhantAuth by hand means learning its client, user, token, and grouping endpoints and how the generated data fits together. Through Jentic you install once, import PhantAuth from the Jentic API Directory, and your agent calls it, with no credentials to configure.
Permission scoping
PhantAuth spans registering clients, generating users, and issuing tokens, and because Jentic One is self-hosted, your own rules decide which operations the agent may call. You can allow reading generated users while withholding operations that register clients, so the agent reaches only what you approved.
Credential isolation
PhantAuth needs no API credentials, so Jentic has nothing to hold or inject for it: requests run without keys. That keeps the test tool simple to wire up while your Jentic One instance still governs which operations run.
Intent-based discovery
Agents search Jentic by intent, such as generating a test user or requesting a token, and Jentic returns the matching PhantAuth operation with typed inputs, so the agent calls the right one without hard-coding endpoints.
Alternatives and complements available in the Jentic catalogue.
Specific to using PhantAuth API through Jentic.
What authentication does PhantAuth use?
PhantAuth's endpoints require no authentication: it is a testing tool that generates disposable users and tokens, so there are no API credentials to provision. Through Jentic, your agent calls the endpoints directly. Check PhantAuth's developer documentation for the details of each endpoint.
Is PhantAuth suitable for production identity?
No. PhantAuth generates random test users and tokens for exercising sign-in and OpenID Connect flows, similar to Lorem Ipsum for authentication. Use it in test and staging environments, not for real user accounts.
What are the rate limits for PhantAuth?
The OpenAPI description does not specify rate limits. Check PhantAuth's developer documentation for any limits before generating users or tokens in bulk.
Is there an MCP server for PhantAuth?
You don't need an MCP server to use PhantAuth with your agent. Through Jentic, your agent finds the client, user, and token operations by intent and calls them directly through your own Jentic One instance.
How do I connect PhantAuth to my agent through Jentic?
To run it on your own infrastructure, install Jentic One from its GitHub repo, then import PhantAuth from the Jentic API Directory. Because the endpoints need no credentials, your agent can start generating test users and tokens straight away.
Can I limit what my agent is allowed to do with PhantAuth?
Yes. Because Jentic One is self-hosted, your own rules decide which PhantAuth operations the agent may call, so you can allow reading generated users while withholding operations that register clients. The controls run on your own instance regardless of the tool needing no credentials.
GET STARTED