Authentiq API

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

✓ Official Vendor SpecIdentity AuthAuthenticationnone14 EndpointsREST

For Agents

Register Authentiq signing keys, issue scoped login challenges, and confirm passwordless authentications for applications using the Authentiq identity protocol.

Connect the Authentiq API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Authentiq 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.

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 Authentiq API API.

Look up, update, or revoke an existing Authentiq key by its public key fingerprint

Issue a passwordless login challenge bound to a scope of identity claims

Retrieve and update the status of an outstanding login or scope job

GET STARTED

Start building with Authentiq API API

Explore with Jentic

View OpenAPI Document

The Authentiq API is the issuer service for the Authentiq passwordless identity platform. It exposes fourteen operations across three resources — keys, login, and scope — that let applications register Authentiq IDs as signing keys, request that a user authenticate against a scope, and complete the resulting login challenge. The protocol uses signed JSON Web Tokens rather than shared passwords, and the API is hosted at the Authentiq issuer endpoint as documented in the public AuthentiqID specification on GitHub.

Use Cases

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

★ Passwordless Login for Web Applications

Web applications integrate Authentiq as a passwordless login provider so users authenticate by approving a signed challenge on a mobile device instead of typing a password. The /scope and /scope/{job} endpoints handle the challenge lifecycle, while /key endpoints register and look up the user's Authentiq ID. A typical integration replaces a password reset flow and shipping it takes two to three days.

Call POST /scope to request the 'email,name' scope, then poll GET /scope/{job} until the user approves on their phone, and validate the returned signed token against the registered key.

Key Management for Issuer-Backed Identities

Applications that distribute signed identities use the /key endpoints to register, rotate, and revoke Authentiq IDs as the canonical signing keys for end users. This replaces ad-hoc public-key directories and gives the application a single API for trust management. Initial setup is typically half a day for the registration flow and a day for revocation handling.

Call POST /key to register a new Authentiq ID, store the returned fingerprint, and later call DELETE /key/{PK} to revoke it when the user offboards.

Step-Up Authentication with Scope Jobs

Applications that need extra confirmation for high-value actions issue a scoped challenge through Authentiq before allowing the action to proceed. The /scope endpoints accept the requested claims and return a job ID; the application polls /scope/{job} until the user signs the challenge or the job times out. Typical integration is two days, including the polling and signature verification.

Call POST /scope with claim 'transaction_signature' and the transaction details, poll GET /scope/{job} for completion, then accept the signed result before executing the transaction.

AI Agent Identity Operations via Jentic

Agents connected through Jentic can issue Authentiq login challenges and check their status programmatically when verifying the human owner of an account. Jentic returns the matching scope or key operation by intent, so the agent does not need to read the AuthentiqID specification on GitHub. End-to-end an agent can request and verify a challenge in under a minute.

Search Jentic for 'request a passwordless login challenge', load /scope, and execute it for the user, then load /scope/{job} to confirm the response.

Key Endpoints

14 endpoints — the authentiq api is the issuer service for the authentiq passwordless identity platform.

METHOD

PATH

DESCRIPTION

POST

/key

GET

/key/{PK}

Look up a key by its public key fingerprint

DELETE

/key/{PK}

Revoke a registered Authentiq key

POST

/login

Complete a passwordless login challenge

POST

/scope

Issue a new scope job requesting identity claims

GET

/scope/{job}

Retrieve the status of an outstanding scope job

DELETE

/scope/{job}

Cancel a pending scope job

POST

/key

GET

/key/{PK}

Look up a key by its public key fingerprint

DELETE

/key/{PK}

Revoke a registered Authentiq key

POST

/login

Complete a passwordless login challenge

POST

/scope

Issue a new scope job requesting identity claims

Why though Jentic?

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

Credential isolation

Authentiq operates on signed JWTs rather than shared secrets, so there are no API keys for Jentic to vault. Jentic instead stores the signing key material agents use to construct request payloads, and ensures private keys never appear in the agent's prompt context.

Intent-based discovery

Agents search Jentic with intents like 'request a passwordless login challenge' or 'register an Authentiq signing key' and receive the matching operation with its input schema, so the agent calls the right endpoint without reading the AuthentiqID protocol spec.

Time to first call

Direct integration with the Authentiq issuer takes two to three days, mostly to handle JWT signing and challenge polling. Through Jentic the search-load-execute flow takes under thirty minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Auth0 Management API

Hosted identity platform with passwordless and full OAuth/OIDC support

Choose Auth0 when the user needs a managed identity platform with broader connectors and dashboards rather than the Authentiq-specific passwordless protocol.

Alternative

Okta API

Enterprise identity provider with SSO, MFA, and lifecycle management

Choose Okta for enterprise SSO and lifecycle management; choose Authentiq when the goal is a lightweight passwordless protocol.

Alternative

OneLogin API

Identity platform with SSO and authentication factors

Choose OneLogin when the user needs traditional SSO and directory integration over passwordless-first flows.

Complementary

Hunter Email Verification API

Verifies email addresses commonly collected during sign-up

Pair Hunter with Authentiq when the user signs up with email — verify the email before issuing the first Authentiq scope challenge.

FAQs

Specific to using Authentiq API API through Jentic.

What authentication does the Authentiq API use?

The API itself is unauthenticated for the public issuer endpoints — security is provided by signed JSON Web Tokens included in request bodies. Each Authentiq ID is a public-key identity that signs requests, so trust is established by verifying the signature against a registered key rather than by an API key or bearer token.

Can I use the Authentiq API for passwordless login?

Yes. Call POST /scope to issue a challenge requesting the claims you need, then poll GET /scope/{job} until the user approves on their Authentiq mobile app. The completed job returns a signed token containing the requested claims that your application can verify against the user's registered key.

What are the rate limits for the Authentiq API?

Authentiq's public issuer documentation does not publish a numeric rate limit. Treat the issuer as fair-use, cache the result of GET /key/{PK} responses, and back off on HTTP 429 or 5xx responses. Avoid tight polling loops on /scope/{job}; use a one-to-three-second poll interval per outstanding job.

How do I register a signing key with the Authentiq API through Jentic?

After running pip install jentic and setting JENTIC_AGENT_API_KEY, search Jentic for 'register an Authentiq signing key', load POST /key, and execute it with the user's Authentiq ID. The response includes the public key fingerprint to store against the user record.

Does the Authentiq API issue tokens itself or just verify them?

It does both within its own protocol. POST /scope and POST /login produce signed responses that the calling application can verify, while POST /key registers the public side of a key pair so subsequent verifications resolve correctly. The API does not issue OAuth or OpenID Connect tokens — it implements the Authentiq passwordless protocol.

Where can I get more details about the Authentiq protocol?

The protocol is documented in the AuthentiqID GitHub repository, including the issuer specification this OpenAPI definition is derived from. The repository describes the JWT-based challenge format and the mobile app interaction model in detail.