Install Jentic One Beta

Connect the AT&T OAuth to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AT&T OAuth, 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%2Fatt.com%2Fatt" | 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%2Fatt.com%2Fatt" | 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 AT&T OAuth API.

Obtain a fresh OAuth 2.0 access token via POST /oauth/v4/token using client credentials

Refresh access tokens before expiry to keep AT&T platform calls authenticated

Issue per-scope tokens for downstream AT&T APIs that require scoped credentials

Centralise AT&T platform authentication for an agent that fans out to multiple AT&T services

Use Cases

Patterns agents use AT&T OAuth API for, with concrete tasks.

GET STARTED

Start building with AT&T OAuth API

Explore with Jentic One

View OpenAPI Document

★ Token Issuance for AT&T Platform Integrations

Any service calling AT&T platform APIs needs an OAuth 2.0 access token before it can issue requests. The AT&T OAuth API's POST /oauth/v4/token implements client-credentials issuance, returning a bearer token tied to the requested scopes. An agent then uses that token in the Authorization header for downstream AT&T calls. Token issuance and refresh logic stays isolated in this single endpoint.

POST to /oauth/v4/token with grant_type=client_credentials, client_id and client_secret, and capture the returned access_token and expires_in

Scheduled Token Refresh

Long-running AT&T integrations need to refresh tokens before expiry to avoid 401 retries. A scheduler agent calls /oauth/v4/token on a cadence shorter than expires_in, caches the latest token, and rotates it into the downstream AT&T API client. This prevents window-edge auth failures during high-volume operations.

Run a scheduled task that requests a new token at expires_in / 2 and updates the cached value used by downstream AT&T API clients

AT&T Token Management via Jentic

Through Jentic, an AI agent calling an AT&T platform API never handles the OAuth client_id or client_secret directly. Jentic stores both in the encrypted vault, calls /oauth/v4/token on demand, and injects the resulting bearer token into downstream AT&T API requests. This collapses AT&T auth into a single Jentic configuration step.

Use Jentic to search 'get an AT&T access token', load POST /oauth/v4/token, and execute with the configured client credentials to retrieve a bearer token

Key Endpoints

1 endpoints — the at&t oauth api is the token endpoint for the at&t developer platform.

METHOD

PATH

DESCRIPTION

POST

/oauth/v4/token

Obtain or refresh an AT&T platform OAuth 2.0 access token

POST

/oauth/v4/token

Obtain or refresh an AT&T platform OAuth 2.0 access token

Why Jentic?

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

Setup

Wiring AT&T OAuth by hand means posting client_id and client_secret to the token endpoint, parsing the bearer token, and reattaching it to downstream calls yourself. Through Jentic you install once, import AT&T OAuth from the API Directory, store the client credentials once, and your agent calls it while Jentic mints and injects the token.

Permission scoping

AT&T OAuth exposes a single token operation that carries its grant type and client credentials in the request body rather than a URL path, so limit the agent to the operation it needs, which is issuing a token. You choose the operations it may call, and this endpoint is the only one exposed.

Credential isolation

Your AT&T client_id and client_secret are stored once, encrypted, by your own Jentic One instance, which calls the token endpoint on demand and injects the resulting bearer token at execution time. Neither credential enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get an AT&T access token', and Jentic returns the POST /oauth/v4/token operation with its grant-type and client-credentials parameters so the call shape is correct on the first try.

FAQs

Specific to using AT&T OAuth API through Jentic.

What authentication does the AT&T OAuth API use?

The AT&T OAuth API itself implements the OAuth 2.0 client-credentials flow - callers pass client_id and client_secret to POST /oauth/v4/token. Through Jentic, both credentials are held in the encrypted vault and the call is made on the agent's behalf, so the secret never enters the agent's context.

Can I refresh an AT&T access token with this API?

Yes. POST /oauth/v4/token supports the OAuth 2.0 token endpoint behaviour, including issuing a fresh access token with the client-credentials grant. Long-running clients re-call this endpoint before expires_in elapses to maintain valid tokens.

What are the rate limits for the AT&T OAuth API?

AT&T throttles token-endpoint calls per client. The spec does not encode a numeric limit - the practical guidance is to refresh tokens at half the expires_in interval and avoid issuing a new token for every downstream call by caching the most recent valid token.

How do I get an AT&T access token through Jentic?

Search Jentic for 'get an AT&T access token', load POST /oauth/v4/token, and execute. Jentic posts grant_type=client_credentials with the stored client_id and client_secret, then returns the access_token and expires_in to the agent.

Is this the only AT&T API available?

This spec covers only the OAuth token endpoint, which is the gating step for the AT&T developer platform. Other AT&T platform APIs (messaging, telco services) sit behind the same OAuth flow and consume the access tokens issued here.

Can I limit what my agent is allowed to do with the AT&T OAuth API?

Yes. The AT&T OAuth API exposes a single operation, POST /oauth/v4/token, which mints an access token using client-credentials passed in the request body. With your self-hosted Jentic One instance, your own rules decide which operations and credentials the agent may use, so you scope the agent to just that token-issuing call and nothing else. Because this endpoint is the only one exposed, the agent can request a token but cannot reach any other AT&T operation you have not allowed.

AT&T OAuth

Name: AT&T OAuth API
Brand: AT&T OAuth
Availability: InStock

Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationoauth21 EndpointsREST

For Agents

Mint OAuth 2.0 access tokens for AT&T platform APIs by calling the AT&T client-credentials token endpoint.

Use for: Get a fresh AT&T access token using client credentials, Refresh an expired AT&T access token, Retrieve a scoped token for a specific AT&T platform API, Check whether an AT&T client id and secret are valid

Not supported: Does not handle SMS, voice, billing, or downstream AT&T platform APIs - use for issuing and refreshing OAuth 2.0 access tokens only.

The AT&T OAuth API is the token endpoint for the AT&T developer platform. It implements the OAuth 2.0 client-credentials flow at /oauth/v4/token, returning the access tokens that other AT&T platform APIs require for authentication. Although the API itself has a single operation, that operation is the gating step for any AT&T platform integration - without it, downstream AT&T services cannot be called.

Jentic One on Github View OpenAPI Document