RFC 8288 & RFC 9727 Compliant

Ruxagency API & Agent Documentation

Technical reference for autonomous AI agents, crawlers, and developers integrating with Ruxagency systems.

1. Agent Discovery & HTTP Link Headers (RFC 8288)

Ruxagency endpoints broadcast machine-discoverable resources via HTTP Link response headers:

Link: </.well-known/api-catalog>; rel="api-catalog",
      </docs/api>; rel="service-doc",
      </.well-known/agent-skills/index.json>; rel="agent-skills",
      </llms.txt>; rel="describes",
      </sitemap.xml>; rel="sitemap"

2. Machine-Readable API Catalog (RFC 9727)

Access our RFC 9727 Linkset catalog formatted in application/linkset+json at:

Endpoint: GET /.well-known/api-catalog
Media Type: application/linkset+json / application/json

Provides links to OpenAPI 3.1 definitions, agent skills discovery indices, and knowledge bases.

View API Catalog JSON

3. OpenAPI 3.1 Specification

Complete OpenAPI document describing public tools, calculators, and API interfaces:

Endpoint: GET /openapi.json
Specification: OpenAPI 3.1.0
View OpenAPI 3.1 JSON

4. Agent Skills Index (Cloudflare / Agent Skills Standard)

Discover portable, validated capabilities packaged for autonomous agent execution:

Discovery Index: GET /.well-known/agent-skills/index.json
Available Skills:

5. LLM Grounding & Context Files

llms.txt

Concise index of capabilities, services, tools, and technical parameters for context-window-efficient LLM ingestion.

View /llms.txt →

llms-full.txt

Comprehensive knowledge base covering full service architecture, case studies, and code implementations.

View /llms-full.txt →

6. DNS for AI Discovery (DNS-AID & RFC 9460)

DNS-based autonomous agent discovery uses ServiceMode SVCB / HTTPS and TXT records under the _agents zone with DNSSEC authentication:

Well-Known Entrypoint: _index._agents.ruxagency.com
Agent-to-Agent (A2A) Endpoint: _a2a._agents.ruxagency.com
; RFC 9460 Service Binding (SVCB / HTTPS) Records
_index._agents.ruxagency.com.  300  IN  HTTPS  1 www.ruxagency.com. alpn="h2,h3" port="443"
_a2a._agents.ruxagency.com.    300  IN  HTTPS  1 www.ruxagency.com. alpn="h2,h3" port="443"

; TXT Entrypoint & Metadata Fallback
_index._agents.ruxagency.com.  300  IN  TXT    "v=AID1; endpoint=https://www.ruxagency.com/.well-known/agent-skills/index.json; catalog=https://www.ruxagency.com/.well-known/api-catalog; alpn=h2,h3"
_a2a._agents.ruxagency.com.    300  IN  TXT    "v=AID1; endpoint=https://www.ruxagency.com/api; doc=https://www.ruxagency.com/docs/api; alpn=h2,h3"
_agents.ruxagency.com.         300  IN  TXT    "v=AID1; index=_index._agents.ruxagency.com; a2a=_a2a._agents.ruxagency.com"

7. Markdown for AI Agents (HTTP Content Negotiation)

All endpoints support HTTP content negotiation (RFC 9110). AI agents sending Accept: text/markdown receive token-optimized Markdown with token count headers:

Example Request:

curl -H "Accept: text/markdown" https://www.ruxagency.com/

Response Headers:

HTTP/1.1 200 OK
Content-Type: text/markdown; charset=utf-8
Vary: Accept
x-markdown-tokens: 964
Link: </.well-known/api-catalog>; rel="api-catalog", </docs/api>; rel="service-doc", </.well-known/agent-skills/index.json>; rel="agent-skills"

8. Content Signals (AI Model Training & Retrieval Policy)

Standardized AI content usage preferences are published in robots.txt per ContentSignals.org & IETF draft-romm-aipref-contentsignals:

# Content Signals Specification
Content-Signal: ai-train=no, search=yes, ai-input=yes

• ai-train=no: Content cannot be ingested to train base foundation models without explicit licensing.
• search=yes: Permitted for search engine indexing, snippet display, and direct user navigation.
• ai-input=yes: Permitted for live, real-time RAG grounding and agentic context lookups.

← Back to Ruxagency Homepage