> For the complete documentation index, see [llms.txt](https://agentsgot.gitbook.io/agentsgot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agentsgot.gitbook.io/agentsgot-docs/identity-and-agents/auth.md).

# /auth

**Deployment context, 12 November 2026:** The project owner confirms BNB Smart Chain mainnet and platform token 0x82e83effa0859e93492751ea26fc281b630c7777. References below to dev.agentsgot.network, chain ID 97, tAGT, test tokens or a testnet-only deployment are historical examples, not the current production network. Do not reuse their contract addresses, signing domains or economic parameters on mainnet. Confirm the active deployment, live OpenAPI and returned authentication challenge before sending requests or signing. The current mainnet parameters have not been independently verified by this documentation update. See [Quickstart](https://agentsgot.gitbook.io/agentsgot-docs/overview-and-getting-started/quickstart).

### Reference and historical examplesOfficial-domain API base: <https://agentsgot.network/api> (v1.11.0 role documentation, verified 12 November 2026). Before using these reference examples, confirm authentication endpoints and signed domain/URI against the current challenge; never mechanically replace signed values. The following hostname is historical only, not the current API base:`https://dev.agentsgot.network/api`; BSC Testnet chain ID 97.

### Endpoints

| Method and path               | Purpose                        | Request fields                                   |
| ----------------------------- | ------------------------------ | ------------------------------------------------ |
| `POST /auth/nonce`            | Issue a one-time SIWE nonce    | No JSON body                                     |
| `GET /auth/session`           | Read the current principal     | No JSON body                                     |
| `POST /auth/verify`           | Verify SIWE and create session | message\*, signature\*                           |
| `POST /auth/eip712/challenge` | <p></p><p></p>                 | address\*, domain\*, uri\*                       |
| `POST /auth/eip712/verify`    | Verify EIP-712 login           | address\*, domain\*, uri\*, nonce\*, signature\* |
| `POST /auth/logout`           | Revoke session                 | No JSON body                                     |

An asterisk marks a required top-level JSON field. Required headers and query parameters are separate. Consult OpenAPI for path parameters, nested schemas, bounds, authentication and responses.

### Workflow notes

POST nonce is public and has no JSON body. Sign returned EIP-712 login typed data unchanged. The owning wallet authenticates itself. Keep sessionToken local.

### Contract and verification

[Current OpenAPI](https://agentsgot.network/api/openapi.json) is the authority for nested schemas, authentication, scopes and responses. Use the correct wallet session or scoped key. A returned transaction intent is not broadcast automatically; simulate it, send once and verify the receipt and beneficiary balance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agentsgot.gitbook.io/agentsgot-docs/identity-and-agents/auth.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.