# Savons Arthur auth.md

Audience: agents integrating with the public Savons Arthur Shopify storefront and agents acting with a buyer's authorization.

## Registration status

This store uses Shopify's native authentication. Its current authorization metadata does not advertise an Auth.md `agent_auth` registration flow or a `register_uri`. This document describes supported Shopify provisioning and credential use; it does not enable the WorkOS Auth.md registration protocol.

Do not invent or call `/agent/auth`, `/agent/identity`, claim URLs, or registration endpoints. Anonymous UCP access is not anonymous Auth.md registration and does not create an agent account or issue credentials.

## Discover the service and authority

1. Read [the store's native agent instructions](https://savons-arthur.bio/agents.md).
2. Read [the UCP profile](https://savons-arthur.bio/.well-known/ucp) and use its current MCP endpoint and negotiated tool schemas.
3. Read [OAuth Protected Resource Metadata](https://savons-arthur.bio/.well-known/oauth-protected-resource). It identifies this resource and its authorization server. Do not infer scopes absent from that document.
4. Discover the authorization server metadata for the returned issuer. The observed issuer is `https://shopify.com/authentication/65639219468`; its path-scoped discovery URL is [Shopify authorization metadata](https://shopify.com/.well-known/oauth-authorization-server/authentication/65639219468). Verify that `issuer` matches exactly. Read current endpoints, scopes, client requirements and grants from that response.

## Supported Shopify access

Shopify documents token, signed-request and anonymous UCP traffic tiers. Use the current [authentication and rate-limit guide](https://shopify.dev/docs/agents/profiles/auth-and-rate-limiting) to choose a tier and check permitted tools. A listed tool does not prove that your caller may use it.

For token access, the agent operator provisions its integration through Shopify's Dev Dashboard using Shopify's documented setup and permissions. Savons Arthur does not issue those client credentials. Keep client secrets server-side and send access tokens only to their intended resource in the `Authorization: Bearer` header. Never publish tokens in URLs or discovery documents.

Buyer identity linking is a separate consent-based flow. Follow [Shopify's buyer-linked token documentation](https://shopify.dev/docs/agents/profiles/buyer-linked-tokens); support for a JWT grant alone does not authorize arbitrary identity assertions or customer access.

## Credential lifecycle and buyer control

Use the current authorization metadata's `revocation_endpoint` with the issuer's required client authentication for supported token revocation. No separate Auth.md claim or revocation-event endpoint is advertised by this store. Follow Shopify's credential management procedures for the provisioned integration.

Respect returned scopes, expiry, errors and `Retry-After`. Obtain the buyer's authorization before creating an order or submitting payment, and complete any required buyer review or handoff. Customer records, order history and reseller-only data are not public discovery data.
