Install Jentic One Beta

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.

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" | sh

Step 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 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

Group mock clients into fleets for multi-application testing

GET STARTED

Start building with PhantAuth API

Explore with Jentic One

View OpenAPI Document

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

GET

/team/{teamname}

Get a group of mock users

GET

/fleet/{fleetname}

Get a group of mock clients

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring PhantAuth by hand means formatting requests against phantauth.net for its user, client, team, and fleet paths and interpreting the generated identity responses yourself; the API needs no auth. Through Jentic you install once, import PhantAuth from the API Directory, and your agent calls it.

Permission scoping

PhantAuth puts the resource id in the URL path (/user/{username}, /client/{client_id}, /team/{teamname}), so a rule can pin your agent to one user, client, or team; the create-user target travels in the request body, so there you limit the agent to the operations it needs. You choose the operations it may call, so creating a user is not included unless you add it.

Credential isolation

PhantAuth needs no credential, so there is none for Jentic to store; if you configure an optional token, it is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'generate a fake test user', and Jentic returns the matching PhantAuth operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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.

Can I limit what my agent is allowed to do with the PhantAuth API?

Yes. Because you run Jentic One yourself, your own rules decide which PhantAuth operations and any optional token the agent may use. PhantAuth puts the resource id in the URL path for GET /user/{username}, GET /client/{client_id}, and GET /team/{teamname}, so a rule can pin the agent to a single user, client, or team, while the create-user target travels in the POST /user body where you restrict it to the operations it needs. Because you choose the operations the agent may call, creating a user or issuing a token stays unavailable unless you add it.

PhantAuth

Name: PhantAuth API
Brand: PhantAuth
Availability: InStock

Browse all Phantauth APIs

Community OpenAPI document · agent-readyIdentity AuthAuthenticationnone10 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Use for: I need to create a test user for authentication, Generate a mock OAuth client for development, Get a test access token for a user, I want to simulate multi-tenant authentication

Not supported: Does not handle real user authentication, production identity management, or secure token signing - use for mock identity generation and testing only.

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.

Jentic One on Github View OpenAPI Document