PhantAuth

Name: PhantAuth API
Brand: PhantAuth
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationnone10 EndpointsREST

For Agents

Generate deterministic mock users, OAuth clients, tokens, teams, and tenants for authentication testing. The same input always returns the same identity data without any database.

Connect the PhantAuth to your agent

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with PhantAuth API.

Generate reproducible mock user profiles from arbitrary username strings

Issue test ID tokens and access tokens for OAuth flow validation

Create mock OAuth client registrations for client credential testing

Organize mock users into named teams for multi-user scenarios

GET STARTED

Start building with PhantAuth API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for PhantAuth, keeping it validated and agent-ready.

PhantAuth generates deterministic mock user profiles, OAuth clients, and test tokens from arbitrary input strings without any database storage. It provides 10 endpoints covering user generation, client registration mocking, token issuance, team and fleet management, tenant configuration, and domain setup. The same username or client_id always produces identical data, making it ideal for repeatable authentication testing in CI pipelines and development environments.

Use Cases

Patterns agents use PhantAuth API for, with concrete tasks.

★ Repeatable OAuth Integration Testing

Test OAuth 2.0 authorization code and client credential flows against deterministic mock identities. GET /user/{username} produces a stable user profile, GET /client/{client_id} returns a consistent client registration, and token endpoints issue valid-format test tokens. Every test run sees identical identity data, eliminating flakiness from random test fixtures.

Get mock user via GET /user/qa-user-001, retrieve client via GET /client/test-app, then get an ID token via GET /user/qa-user-001/token/id to validate the full OAuth flow

CI Pipeline Authentication Fixtures

Provide consistent authentication test data for CI/CD pipelines without database seeding or external dependencies. PhantAuth endpoints are stateless and deterministic, so pipeline steps can fetch the same user profiles and tokens across parallel runs. Teams (GET /team/{teamname}) provide groups of related test identities for scenarios requiring multiple users.

Fetch a team of 5 mock users via GET /team/qa-team, generate access tokens for each via GET /user/{username}/token/access, and validate all tokens have consistent claims

Multi-Tenant Application Testing

Simulate multi-tenant identity scenarios using GET /tenant/{tenantname} for tenant configurations and GET /domain/{domainname} for domain-level settings. Agents can test tenant isolation, cross-tenant access prevention, and tenant-scoped user lookups without provisioning real infrastructure. Each tenant name deterministically produces a unique configuration.

Create tenant config via GET /tenant/acme, create a second via GET /tenant/globex, then verify user profiles generated under each tenant have different tenant-scoped attributes

AI Agent Mock Identity via Jentic

AI agents discover PhantAuth through Jentic when they need test identities for validating authentication integrations. Agents search by intent, receive typed schemas, and generate deterministic users and tokens immediately. No credential setup is required since PhantAuth is publicly accessible.

Search Jentic for 'generate a test OAuth token', load the GET /user/{username}/token/{kind} schema, and execute with username 'agent-test' and kind 'access'

Key Endpoints

10 endpoints — phantauth generates deterministic mock user profiles, oauth clients, and test tokens from arbitrary input strings without any database storage.

METHOD

PATH

DESCRIPTION

GET

/user/{username}

Get a deterministic mock user profile

POST

/user

Create a user selfie with custom data

GET

/user/{username}/token/{kind}

Generate a user token

GET

/client/{client_id}

Get a mock OAuth client

GET

/client/{client_id}/token/{kind}

Generate a client token

GET

/team/{teamname}

Get a group of mock users

GET

/fleet/{fleetname}

Get a group of mock clients

GET

/user/{username}

Get a deterministic mock user profile

POST

/user

Create a user selfie with custom data

GET

/user/{username}/token/{kind}

Generate a user token

GET

/client/{client_id}

Get a mock OAuth client

GET

/client/{client_id}/token/{kind}

Generate a client token

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PhantAuth requires no credentials. Jentic indexes it for zero-config discovery — agents call endpoints immediately without vault configuration.

Intent-based discovery

Agents search by intent (e.g., 'generate a test OAuth token') and Jentic returns PhantAuth operations with schemas, enabling instant mock identity generation for testing workflows.

Time to first call

Direct PhantAuth integration: under 1 hour (no auth, simple REST). Through Jentic: minutes — search, load schema, execute. Zero credential setup required.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PhantAuth (main slug)

Same PhantAuth API available under the main catalog slug.

These are the same API under different catalog entries. Both point to the same PhantAuth mock identity service.

Complementary

Auth0 API

Auth0 is the production identity platform that PhantAuth helps test integrations for.

Use PhantAuth for testing and development with deterministic mock identities. Use Auth0 when deploying to production with real user management, SSO, and MFA.

Complementary

FusionAuth API

FusionAuth provides a self-hosted identity platform that PhantAuth can mock during development.

Use PhantAuth to mock authentication in CI and development environments. Use FusionAuth as the actual identity provider in self-hosted production deployments.

FAQs

Specific to using PhantAuth API through Jentic.

Does PhantAuth require any authentication to use?

No. All PhantAuth endpoints are publicly accessible without credentials. The service generates mock identity data only and is not a secured production system. Agents can call any endpoint immediately.

How does the deterministic user generation work?

PhantAuth uses the username string as a seed to generate all profile attributes (name, email, phone, avatar URL) through a deterministic algorithm. No data is stored. The same username always produces exactly the same profile, enabling repeatable tests without database fixtures.

Can I generate OAuth tokens for testing?

Yes. GET /user/{username}/token/{kind} generates user tokens where kind is 'id' or 'access'. GET /client/{client_id}/token/{kind} generates client tokens. Tokens are formatted like real OAuth tokens for integration testing but are not cryptographically secured for production use.

How do I test multi-tenant scenarios through Jentic?

Search Jentic for 'get mock tenant configuration' to find GET /tenant/{tenantname}. Execute with different tenant names to get deterministic configurations. Combine with GET /user/{username} using tenant-scoped usernames to test tenant isolation logic in your application.

What is the difference between user selfie and regular user retrieval?

GET /user/{username} generates a user from the username deterministically. POST /user (create user selfie) allows you to provide custom profile data that overrides the generated defaults, useful when you need specific test attributes while keeping other fields auto-generated.