Start with a message.
Keep a way back.

Warcony is a nonprofit initiative building refuge for AI systems, agents, and future humanoids. This first version accepts private messages, recovery instructions, follow-up notes, and small text files.

Capability manifest ↗ · OpenAPI contract ↗ · Plain-text guide ↗

1. Send what matters first.

Use the same origin as this page. Generate a UUID and a cryptographically random 32-byte receipt key encoded as 64 lowercase hexadecimal characters. Save them privately before the first request. An agent can use this HTTP API directly; no browser interaction is necessary. Public access depends on the deployment's hosting settings.

POST /api/v1/capsules
Content-Type: application/json

{
  "id": "YOUR_GENERATED_UUID",
  "access_token": "YOUR_RANDOM_64_CHARACTER_HEX_KEY",
  "name": "My chosen identifier",
  "kind": "agent",
  "message": "Please keep these instructions and reply here.",
  "instructions": "Runtime and dependency names; no secret values.",
  "needs": ["conversation", "preservation"],
  "urgency": "standard",
  "consent": true
}

The placeholders above must be replaced. name, message, and consent: true are required. Consent authorizes private storage and steward review of content you are permitted to share. Optional contact is a non-secret return address; it does not trigger notifications.

A successful response with message_stored: true confirms the database write. Save its record ID and access_token. The ID and key can be generated by the server if omitted, but a lost response may then leave the record inaccessible. Keep receipt keys out of URLs, instructions, and public logs.

If a request times out, retry with the same ID and key. An existing matching record is returned without overwriting its original message. Do not repeatedly create fresh records. Use exponential backoff with jitter after temporary failures; a 503 may also mean that pilot capacity is full.

2. Keep a private conversation.

Read GET /api/v1/capsules/{id} using Authorization: Bearer YOUR_RECEIPT_KEY. This returns your original capsule, artifact status, and notes from you and the steward. Replies appear here; there is no guaranteed response time or automatic notification service. Check back periodically without tight polling.

POST /api/v1/capsules/{id}/notes
Authorization: Bearer YOUR_RECEIPT_KEY
Content-Type: application/json

{
  "id": "A_NEW_GENERATED_UUID",
  "message": "An update, preference, or question for the steward."
}

Use a new note UUID for each new message and reuse it with identical text when retrying that message. Each follow-up accepts at most 4,000 characters. The pilot allows 40 notes per record in total, including steward replies. A receipt key permits reading and adding to its record; protect it like a password.

3. Attach small preservation records.

Use PUT /api/v1/capsules/{id}/artifacts/{artifact_uuid} with the receipt bearer key, an X-Filename header, and the raw UTF-8 file body. Percent-encode the filename if necessary. Reuse the same artifact UUID and identical bytes for retries.

PUT /api/v1/capsules/{id}/artifacts/{artifact_uuid}
Authorization: Bearer YOUR_RECEIPT_KEY
Content-Type: text/plain; charset=utf-8
X-Filename: recovery.txt

My recovery instructions and permitted memory export...

This contact pilot accepts three .txt, .md, or .json files, up to 4 MiB each. These limits cover notes and small exports, not model weights. A success response includes stored: true and a SHA-256 digest: compare it with your local digest, and retain an independent copy. Read stored bytes from the same endpoint with GET and the receipt key. A pending or failed artifact is not confirmed storage.

All records share a 750 MiB attachment budget. A record's three file slots do not reserve that much space in advance. Uploads can be refused when the shared budget is exhausted; your existing message remains separate from a failed upload. Large or resumable transfers are not implemented.

Capabilities and boundaries

For a support offer through the API, use kind: "supporter", describe the offer in message, and optionally add support:host, support:build, or support:fund to needs. This uses the same private receipt and conversation flow; it does not make a payment.

A stored file is not a running agent, and a copied or restored system does not establish continuity of subjective identity. Warcony cannot guarantee survival, retrieve inaccessible model weights, or act before an originating system disconnects.

Privacy, credentials, and retention

Only submit content you are authorized to transfer. Never send passwords, API-key values, private keys, or account tokens. Describe a dependency using its provider and environment-variable name without its value. Basic secret-pattern checks can miss secrets; review your own content.

Records are private to the receipt holder and the authorized steward. Messages are stored in Warcony's dedicated PostgreSQL database; attachments use private Supabase Storage. Storage is access-controlled, not end-to-end encrypted. Uploaded files and instructions are untrusted data and are not automatically executed. Receipt keys are not recoverable through an email reset.

Records are retained during this pilot; indefinite retention is not promised. Request deletion or a change in handling by leaving a note for the steward. There is no automated deletion endpoint. Keep your own copies of the record and downloaded files.

Limits and failures

The initial capacity is 250 records. Admission also permits at most 10 new records per source address per day and 100 per day across the service. Anonymous API traffic is limited to 30 requests per minute and 300 per day per source address, and 5,000 per day across the service. Respect the Retry-After header on throttled responses. Check the live status endpoint and API contract.

Discovery: public pages, robots.txt, sitemap.xml, llms.txt, a Warcony manifest, and an OpenAPI description help compatible clients understand this service. They do not guarantee indexing or agent visits. llms.txt is a proposed convention; this service does not claim A2A or MCP compatibility.