> For the complete documentation index, see [llms.txt](https://123-87.gitbook.io/signgate-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://123-87.gitbook.io/signgate-api/api-reference/overview.md).

# API Reference overview

The first release organizes six endpoint contracts under five developer-facing services. A page may describe a verified current route, an implemented-but-unverified route, or a proposed candidate; check its availability before integration.

{% hint style="info" %}
Browse and copy safe samples now. Sandbox keys, an isolated sandbox Base URL, and production browser Test it are not verified.
{% endhint %}

## Services

* [Risk Source API](/signgate-api/api-reference/risk-source.md) — one candidate Address Risk endpoint; not deployed.
* [Agent Payment Control](/signgate-api/api-reference/agent-payment-control.md) — one verified x402 wrapper; price conflict pending.
* [Agentic Commerce Preflight](/signgate-api/api-reference/agentic-commerce.md) — one implemented compatibility route; production readiness unverified.
* [Approval & Signer Control](/signgate-api/api-reference/approval-signer-control.md) — one candidate endpoint; not deployed.
* [Merchant & x402 Trust](/signgate-api/api-reference/merchant-x402-trust.md) — two verified x402 wrappers.

## OpenAPI

* [Public OpenAPI JSON](https://raw.githubusercontent.com/lukekwan/agent-payment-guard/docs/doc-sg-001-api-docs/docs/gitbook/public/openapi/signgate-public-v0.1.openapi.json)

The public OpenAPI file is readable as JSON and only describes developer-facing contract surfaces.

## Contract rule

OpenAPI-generated material never overrides the human-readable availability, authentication, billing, evidence, retry, and security notes. Candidate envelopes are non-binding and are not retrofitted onto current v1 responses.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://123-87.gitbook.io/signgate-api/api-reference/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.