# G-ATAI auth.md

Audience: AI assistants reading public G-ATAI information or helping an explicitly consenting user choose a business consultation. The resource origin is https://www.g-atai.com.

## Public access method

Public pages, article metadata and availability reads use anonymous HTTPS GET requests. No registration, account, API key, bearer token or identity assertion is required. Do not send user passwords, provider tokens or personal information with these reads.

- [API catalog](https://www.g-atai.com/.well-known/api-catalog) lists the public read endpoints.
- [OpenAPI description](https://www.g-atai.com/openapi.json) documents their parameters, responses and limitations.
- [Public reading directory](https://www.g-atai.com/llms.txt) links to company information, services, projects and native language editions.
- Request a public page with `Accept: text/markdown` to receive its Markdown representation. HTML is the default for browsers.

## Registration and credential provisioning

Agent registration and credential provisioning are not offered on this marketing website. There is no supported registration endpoint, token endpoint, OAuth issuer, claim ceremony, ID-JAG exchange or verified-email credential flow for external agents. Anonymous public retrieval is the only supported agent access method. OAuth metadata is therefore not advertised.

The company's Google Calendar authorization belongs to the meeting organizer. It is not a visitor identity provider and must never be used as an external agent's authorization server. Internal administration and company systems use separate controls and are not part of this public catalog.

## Reading available meeting times

`GET /api/booking/availability?providerDate=YYYY-MM-DD` returns provider time slots and unavailable slots for a supported booking date. The returned `providerTimezone` identifies the timezone of those slots. Convert it to the user's timezone before presenting a time. This read does not reserve a meeting, create a Google Meet link, send an email or reveal attendees.

Use the returned slot list rather than inventing availability. A temporarily unavailable Calendar service returns HTTP 503. Refresh shortly before the user confirms: a displayed slot can be taken by another visitor.

## Booking and other actions

After the user chooses a service, open the appropriate existing flow:

- [Strategy consultation](https://www.g-atai.com/booking)
- [AI agents](https://www.g-atai.com/booking/agents)
- [Business automation](https://www.g-atai.com/booking/business)
- [Custom AI development](https://www.g-atai.com/booking/build-ai)

Let the user review their details, timezone and meeting time and confirm on the website. Do not treat a read request as a booking confirmation. Booking uses the existing protected form, fresh availability validation and the established Google Calendar/Meet workflow. A real successful booking can send the meeting confirmation email. Do not bypass form protections or probe registration/booking POST endpoints during passive scans.

The newsletter stores subscriptions without sending automatic replies. Contact submissions go to the company inbox; they do not authorize autonomous email campaigns or outbound replies to visitors.

## Content use and request behavior

Public content may be used for search and AI answers (`search=yes, ai-input=yes`). Training use is reserved (`ai-train=no`). Follow [robots.txt](https://www.g-atai.com/robots.txt), respect caching headers, use moderate request rates and back off after HTTP 429 or 503. Cite the canonical HTML page rather than the Markdown URL. A 401 or 403 from a private endpoint does not grant permission to bypass its access controls.
