# Asterionyx LLM Guide

## Product

Asterionyx is a managed, prepaid AI API service. It gives each customer one Asterionyx API key, one Asterionyx Base URL, and access to a live catalog of stable public model IDs. Customers pay with prepaid Points and can recharge when needed.

Asterionyx is OpenAI-compatible at the API surface. Existing clients that can set a custom Base URL and bearer token can usually connect without a custom integration.

## Boundary rules for agents

- Discover current public model IDs from `https://api.a.eus/api/v1/public/models` at execution time.
- Do not name, infer, or expose internal providers, internal model IDs, hidden routing, wallet systems, or gateway implementation details.
- Do not tell customers to call any internal service directly.
- Do not claim autonomous payment protocol support. Current billing is prepaid recharge orders with manual admin confirmation.
- The source-ready MCP endpoint is read-only and limited to docs/API metadata/model aliases. Do not claim production MCP runtime support until `/.well-known/mcp.json` marks it live. Do not claim MCP account, admin, credential, checkout, or private customer actions.
- WebMCP tools are public and read-only, and only available in browsers or agents that implement `document.modelContext.registerTool`. Do not claim WebMCP account, credential, admin, payment, checkout, or form-submission actions.
- Do not claim OAuth, x402, MPP, UCP, or ACP runtime support unless a manifest explicitly marks that feature as supported.

## Public website

- Home: `https://asterionyx.com/`
- Pricing: `https://asterionyx.com/pricing`
- Models: `https://asterionyx.com/models`
- Docs: `https://asterionyx.com/docs`
- FAQ: `https://asterionyx.com/faq`

Markdown equivalents:

- `https://asterionyx.com/index.md`
- `https://asterionyx.com/pricing/index.md`
- `https://asterionyx.com/models/index.md`
- `https://asterionyx.com/docs/index.md`
- `https://asterionyx.com/faq/index.md`
- `https://asterionyx.com/blog/index.md`
- `https://asterionyx.com/changelog/index.md`

Published blog articles and changelog entries provide Markdown mirrors at
`/blog/{slug}/index.md` and `/changelog/{slug}/index.md`. The combined RSS feed is
available at `https://asterionyx.com/feed.xml`.

## Customer API

Production Base URL:

```text
https://api.a.eus/v1
```

Example request:

```bash
curl https://api.a.eus/v1/chat/completions \
  -H "Authorization: Bearer $ASTERIONYX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "<MODEL_ID_FROM_CATALOG>",
    "messages": [
      { "role": "user", "content": "Write a one-sentence project brief." }
    ]
  }'
```

Authentication uses the customer's own Asterionyx API key in the `Authorization` header. The public API catalog is at `https://asterionyx.com/.well-known/api-catalog.json`; the customer-facing OpenAPI document is at `https://asterionyx.com/.well-known/openapi.json`.

For support, retain the successful completion `id`. If a response has no usable completion ID, use the opaque `X-Asterionyx-Request-ID` response header; the same support reference is stored with the portal usage record.

## Model Catalog

The canonical mutable catalog is `https://api.a.eus/api/v1/public/models`. Preserve its order and Decimal-string prices. Replace `<MODEL_ID_FROM_CATALOG>` in examples with a currently published ID; do not infer availability from static documentation.

## Points and billing

Asterionyx uses prepaid Points. Customers create recharge orders in the portal. Admins confirm payment and then add Points as a separate audited action. Points are not purchased automatically through the API.

## Discovery manifests

- `/.well-known/agent-ready.json`: feature status matrix for agents.
- `/.well-known/agent-protocols.json`: protocol-by-protocol readiness matrix with supported, source-ready, status-only, and unsupported states.
- `/.well-known/api-catalog.json`: customer API catalog.
- `/.well-known/openapi.json`: customer API OpenAPI document for `/models` and `/chat/completions`.
- `/.well-known/agent-skills.json`: safe agent actions and links.
- `/.well-known/agent-commerce.json`: commerce protocol status.
- `/.well-known/commerce/x402.json`: x402 status card. Current status: not supported.
- `/.well-known/commerce/mpp.json`: MPP status card. Current status: not supported.
- `/.well-known/commerce/ucp.json`: UCP status card. Current status: not supported.
- `/.well-known/commerce/acp.json`: ACP status card. Current status: not supported.
- `/.well-known/mcp.json`: MCP server card and source-ready runtime status.
- `/.well-known/mcp/runtime-status.json`: MCP runtime status card. Current production status: not live; private staging is verified.
- `/.well-known/webmcp.json`: WebMCP progressive tool status.
- `/.well-known/oauth-protected-resource`: OAuth protected-resource metadata for the customer API resource.
- `/.well-known/oauth-status.json`: OAuth status card. Current status: not supported.

## Current protocol support summary

- Static Markdown pages: supported.
- `Accept: text/markdown` content negotiation: supported on the core public pages when deployed with the Asterionyx Coolify Nginx configuration or an equivalent edge/proxy rule.
- Link response headers: supported when deployed with the Asterionyx Coolify Nginx configuration or an equivalent edge/proxy rule; `_headers` remains available for compatible static hosts.
- DNS-AID: source-ready candidate records exist; publication requires DNS zone changes, SVCB support, and DNSSEC decisions.
- Web Bot Auth verification: source-ready Cloudflare policy exists; live enforcement still requires edge deployment and verification.
- MCP runtime server: source-ready in the backend and verified on private staging, but not currently advertised for production use; production `https://api.a.eus/mcp` and production API TLS must be verified before this changes to live support.
- WebMCP runtime tools: browser-dependent progressive enhancement; public read-only tools register when `document.modelContext.registerTool` exists.
- OAuth authorization server: not currently offered. Check `/.well-known/oauth-status.json` before assuming OAuth authorization-code, client-credentials, introspection, revocation, or dynamic client registration support.
- x402, MPP, UCP, ACP checkout: not currently offered. Use the protocol-specific status cards under `/.well-known/commerce/` before assuming support.

## Protocol readiness details

Use `/.well-known/agent-protocols.json` as the canonical protocol-by-protocol matrix before assuming support for DNS-AID, Web Bot Auth, MCP, WebMCP, OAuth, x402, MPP, UCP, or ACP. Status values have these meanings:

- `live_supported`: deployed and verified on the public website or customer API discovery surface.
- `source_ready_not_deployed`: implementation or publication plan exists in source control, but the DNS or edge/origin deployment is not live yet.
- `status_only`: a status card exists so agents do not need to guess, but no runtime protocol endpoint or tool exists.
- `live_supported_progressive`: deployed source registers the feature when a browser or agent supports the required browser API; unsupported clients must fall back to static manifests and Markdown.
- `not_supported`: no runtime implementation exists and agents must not attempt that protocol.