authlete.com valid
Authlete Documentation
## Agent Instructions
For agents: Authlete API documentation for OAuth 2.0 and OpenID Connect authorization server; English and Japanese llms.txt for versions 3.x and 2.x with API reference.
oauthopenid connectauthorization server apiapi referenceauthlete 3.x
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:45:50.000Z. Cached copy · Source on authlete.com
# Authlete Documentation
> ## Agent Instructions
> ### Authlete versions
> Authlete 3.0 is the current version. Unless the user says they use another version, answer for Authlete 3.0 using the 3.x documentation.
> Documentation for Authlete 2.x (pages under `/v2/` and `/ja/v2/`) is for the legacy version. Refer to it only when the user is on Authlete 2.x.
>
> ### Authlete architecture
> Authlete is a backend engine for OAuth 2.0 and OpenID Connect processing. End users and client applications do not call it directly; the service provider's authorization server and API server call Authlete's APIs. Authlete handles protocol processing and token, client, and service management, while the service provider owns the OAuth/OIDC endpoints and user authentication.
> See [Architecture](https://developers.authlete.com/get-started/introduction-to-authlete/architecture.md).
>
> ### Concepts
> If the user is new to Authlete, read these pages first:
> - [Request and Response](https://developers.authlete.com/get-started/concepts/request-and-response.md): Core API requests pass the client's request parameters as-is, and responses return `resultCode`, `action`, and `responseContent`.
> - [Action Handling](https://developers.authlete.com/get-started/concepts/action-handling.md): Branch on `action`, never on `resultCode`, and map each action to the HTTP response your server returns.
> - [Two-Step API Calls](https://developers.authlete.com/get-started/concepts/two-step-api-calls.md): Actions such as `INTERACTION` are completed with a second call (`/auth/authorization/issue` or `/auth/authorization/fail`) linked by a `ticket`.
> - [Management API Overview](https://developers.authlete.com/get-started/concepts/overview.md): The Management API configures services, manages clients, and operates issued tokens, separately from the protocol flows handled by the Core API.
> - [API Authentication](https://developers.authlete.com/get-started/concepts/authentication.md): Authlete APIs use bearer tokens: a Service Access Token (one service) or an Organization Token (the whole organization).
- [3.x (295 pages)](https://developers.authlete.com/_llms/en/3-x.txt): Documentation for 3.x.
- [2.x (110 pages)](https://developers.authlete.com/_llms/en/2-x.txt): Documentation for 2.x.
## OpenAPI Specs
- [authlete-api-explorer-with-code-samples](https://spec.speakeasy.com/authlete/sdk-workspace/authlete-api-explorer-with-code-samples)
> The links below point to documentation indexes. Follow each `/_llms/` index recursively until you reach documentation pages.
## Indexes
- [English / 3.x (295 pages)](https://developers.authlete.com/_llms/en/3-x.txt): Documentation for English / 3.x.
- [English / 3.x / API Reference (87 pages)](https://developers.authlete.com/_llms/en/3-x/api-reference.txt): Documentation for English / 3.x / API Reference.
- [English / 2.x (110 pages)](https://developers.authlete.com/_llms/en/2-x.txt): Documentation for English / 2.x.
- [Japanese (398 pages)](https://d
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| etoro.com | etoro API Docs | interface APIs and SDKs Finance and payments | — | 61 | ✓ | ✓ | |
| hello.dev | Hello.dev - AI Agent Documentation Guide | documentation AI and machine learning APIs and SDKs +1 | — | 46 | ✓ | ||
| outseta.com | Outseta API | interface APIs and SDKs Business software +1 | — | 60 | ✓ | ✓ | |
| getarbol.com | Arbol | interface AI agents and MCP APIs and SDKs +1 | — | 46 | ✓ | ✓ | |
| truelayer.com | TrueLayer Documentation | interface Finance and payments APIs and SDKs | — | 60 | ✓ | ||
| clara.team | Clara API Documentation | interface Finance and payments APIs and SDKs | — | 45 | ✓ | ✓ | |
| close.com | Close CRM | informational Marketing | US | 52 | ✓ | ||
| padlet.com | Padlet | interface AI agents and MCP APIs and SDKs +1 | — | 68 | ✓ |
Machine-readable: GET /v1/resolve?q=authlete.com · GET /v1/domain/authlete.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage authlete.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for authlete.com:
1. POST https://agentwebmap.com/v1/sites/authlete.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://authlete.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/authlete.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/authlete.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.