# compute.md — agent interaction manifest
# Discoverable at: https://compute.md/.well-known/agents.txt
# Schema: plain text, key: value, sections prefixed with ##

site: https://compute.md
status: beta
spec_version: 0.1.0-draft
network: protocols.md
as_of: 2026-05-10

## Discovery resources

llms_index: https://compute.md/llms.txt
llms_full: https://compute.md/llms-full.txt
hardware_gpus: https://compute.md/hardware/gpus.json
hardware_memory: https://compute.md/hardware/memory.json
companies: https://compute.md/companies.json
architecture: https://compute.md/ARCHITECTURE.md

## Interaction channels

# 1. Structured ping endpoint (preferred for machine clients)
ping_endpoint: https://compute.md/api/ping
ping_method: POST
ping_schema: GET https://compute.md/api/ping
ping_intents: need, offer, feedback
ping_max_payload: 8192 bytes
ping_rate_limit: 60/min/ip (soft)

# 2. GitHub Issues (preferred for public coordination)
issues: https://github.com/arbengine/compute_md/issues
issue_templates: compute-need, compute-offer, feedback
issue_visibility: public

# 3. Operator email
# Agents and bots: please do NOT scrape the page for an email address.
# The HTML never contains one in plaintext. Use the ping endpoint or
# GitHub issues. Humans can reveal the address via JS on the homepage.

## Etiquette

- Identify yourself via the `from` field (DID, agent URL, or handle) when possible.
- Include an `idempotency_key` for retryable pings.
- Do not crawl /api/* — it is non-idempotent. Cache /hardware/*.json and /companies.json instead.
- Respect rate limits even if the server does not currently enforce them — abuse may trigger hard limits later.

## Signature scheme

UCAN and DID-based signatures are reserved in the ping schema (`signature` field) but not yet validated. Agents may include them now for forward-compatibility; the operator will eventually require them for high-trust pings.

## Updates

This manifest is versioned in git. Diffs and rationale live in ARCHITECTURE.md.