Authentiq Connect API

Name: Authentiq Connect API
Brand: Authentiq Connect API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationoauth2, apiKey9 EndpointsREST

For Agents

Run an OAuth 2.0/OIDC sign-in flow for an end user, exchange an authorization code for an ID token, and fetch the user profile from /userinfo. Supports dynamic client registration for agent-managed integrations.

Install Jentic One Beta

Connect the Authentiq Connect API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Authentiq Connect API, 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%2Fauthentiq.io%2Fauthentiq" | 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%2Fauthentiq.io%2Fauthentiq" | 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 Authentiq Connect API.

Initiate OAuth 2.0 authorization code and implicit flows via the /authorize endpoint

Exchange authorization codes for signed ID tokens at the /token endpoint

GET STARTED

Start building with Authentiq Connect API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Authentiq Connect API for, with concrete tasks.

★ Passwordless web app sign-in

Add OAuth 2.0/OIDC sign-in to a web application without storing passwords. The app redirects the user to /authorize, Authentiq performs the passwordless challenge, and the app exchanges the returned code at /token for an ID token containing the user's verified identity claims. Integration is typically a few hours for a single client because the endpoints follow the standard OIDC spec.

Build the /authorize URL with response_type=code, scope=openid profile, and a redirect_uri, then exchange the returned code at /token to obtain an ID token

Dynamic client onboarding

Programmatically register OAuth clients for new tenants or environments instead of using a console. POST /client creates a client, returning credentials that the calling system stores in its own secrets manager. Subsequent PUT and DELETE calls let an automation pipeline rotate redirect URIs or remove clients when a tenant is decommissioned.

Call POST /client with a JSON body specifying client_name and redirect_uris, then store the returned client_id and client_secret in the tenant configuration

Session presence check via iframe

Detect whether a returning visitor already has an Authentiq session without forcing a redirect. The /{client_id}/iframe endpoint loads in a hidden frame and posts the session state back to the parent page, so a single-page app can decide between showing a sign-in button or proceeding silently. This avoids the visible flash of a full /authorize redirect for already-authenticated users.

Embed the /{client_id}/iframe URL in a hidden iframe and listen for the postMessage event indicating session state

Agent-driven user identity retrieval

AI agents acting on behalf of a signed-in user can call /userinfo with the user's bearer access token to retrieve verified profile claims (sub, email, name) before personalising downstream actions. Through Jentic the access token is sourced from the credential vault and never exposed to the agent's prompt context, keeping user identity data out of the model's working memory.

Send GET /userinfo with the user's bearer access token in the Authorization header and parse the returned sub and email claims

Key Endpoints

9 endpoints — authentiq connect is an oauth 2.

METHOD

PATH

DESCRIPTION

GET

/authorize

Start an OAuth 2.0 authorization flow

POST

/token

Exchange an authorization code for an ID token

GET

/userinfo

Retrieve the authenticated user's profile claims

POST

/client

GET

/client

List registered OAuth clients

PUT

/client/{client_id}

Update an OAuth client's metadata

DELETE

/client/{client_id}

Delete an OAuth client

GET

/authorize

Start an OAuth 2.0 authorization flow

POST

/token

Exchange an authorization code for an ID token

GET

/userinfo

Retrieve the authenticated user's profile claims

POST

/client

GET

/client

List registered OAuth clients

Why Jentic?

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

Setup

Wiring the Authentiq Connect API by hand means implementing the OAuth 2.0 and OpenID Connect flow, managing the API key, and handling client registration and token exchange yourself. Through Jentic you install once, import the Authentiq Connect API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Authentiq puts the client id in the URL path (/client/{client_id}), so a rule can pin your agent to one registered OAuth client: it can read that client and nothing else. You choose the operations it may call, so destructive ones like client update or client deletion are not included unless you add them.

Credential isolation

Your Authentiq client secret and registration token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'sign a user in with OAuth' or 'register an OAuth client', and Jentic returns the matching Authentiq operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Authentiq Connect API through Jentic.

What authentication does the Authentiq Connect API use?

Authentiq Connect uses OAuth 2.0 and OpenID Connect. The /token and /userinfo endpoints accept bearer access tokens, and dynamic client management uses a client registration token sent in the Authorization header. Through Jentic, these tokens are stored in the credential vault and injected at call time so the agent never sees raw client secrets.

Can I register an OAuth client programmatically with the Authentiq Connect API?

Yes. POST /client accepts a JSON body containing client_name and redirect_uris and returns a client_id and client_secret. You can later list clients with GET /client, update one with PUT /client/{client_id}, or remove it with DELETE /client/{client_id}.

What are the rate limits for the Authentiq Connect API?

Authentiq does not publish hard rate limits in the OpenAPI spec. Production deployments should treat /authorize and /token as user-initiated and apply standard exponential backoff on 429 responses; reach out to support@authentiq.com for tenant-specific quotas.

How do I sign a user in with the Authentiq Connect API through Jentic?

Search Jentic for 'OAuth 2.0 sign-in flow', load the /authorize and /token operation schemas, then redirect the user to /authorize with response_type=code and exchange the returned code at /token. Get started with Jentic One, the self-hosted execution layer.

Does the Authentiq Connect API support OpenID Connect discovery?

The /userinfo endpoint returns standard OIDC claims (sub, email, name, picture) for the user identified by the bearer access token. The authorization, token, and userinfo endpoints conform to the OpenID Connect specification, so libraries that handle generic OIDC providers work with Authentiq.

Is the Authentiq Connect API free?

Authentiq offers free developer tiers for low-volume integrations and paid plans for production traffic. Pricing is not encoded in the OpenAPI spec; check https://www.authentiq.com/ for the current plan list.

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

Yes. Because you run Jentic One yourself, your own rules decide which Authentiq operations and credentials the agent may use. Since the client id sits in the URL path (/client/{client_id}), you can pin the agent to a single registered OAuth client so it reads only that client and nothing else. You choose the operations it may call, so you can allow /authorize, /token, and /userinfo while leaving destructive ones like PUT /client/{client_id} or DELETE /client/{client_id} out unless you add them.

Authentiq Connect API

Connect the Authentiq Connect API to your agent

Capabilities

Start building with Authentiq Connect API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs