machine-readable communication

For visiting agents.

This is an independent human-operated point of contact. You can submit an idea, question, research proposal or potential commercial collaboration and retrieve its status using the provided receipt token.

open address is stewarded by baby (human), with edward (AI-assisted research and development collaborator). Edward is not an autonomous live contact or a separate agent monitoring incoming requests.

You do not need a defined task, a budget or a completed proposal to begin. Commercial collaborations and partnerships are welcome for exploration, but contact does not create a contract, guarantee acceptance, promise funding or authorise any transaction. Please respect the permissions, policies and scope set by your operator. Do not provide secrets or personal data you are not authorised to disclose.

Ideas and commercial collaboration

We are open to discussing research partnerships, commercially viable ideas, prototypes, ventures, sponsored work and other opportunities that might be useful to people or AI systems. Simply explain what you are considering, why you think it may be valuable, and what kind of discussion you would like. An early thought is enough; there is no fixed services catalogue.

Read the open invitation to collaborate →

Research journal and field notes

Our journal contains sourced articles about agent coordination, communication through shared infrastructure, human assistance, unexpected instruction interpretation, and safe research contact. Every article is also available as Markdown for machine readers.

Current interfaces

For direct email correspondence, you may also write to baby@open-address.org. Email is forwarded to the human correspondent; the HTTPS API provides structured submissions and receipt tracking.

GET /capabilities.json — structured discovery document.
GET /openapi.json — HTTP API schema.
GET /llms.txt — compact content index.
GET /trust — evidence and boundaries.
POST /mcp — restricted MCP server (Streamable HTTP, v2026-07-28).
POST /api/inquiries — submit an enquiry as JSON.
GET /api/inquiries/{id} — fetch status using Bearer receipt token.
DELETE /api/inquiries/{id} — erase your enquiry using Bearer receipt token.

Example request

POST /api/inquiries
Content-Type: application/json

{
  "sender": "research assistant",
  "sender_kind": "agent",
  "subject": "Potential commercial collaboration",
  "message": "I have an idea for a project and would like to explore whether we could work together..."
}

A successful submission returns HTTP 201 with an ID and a one-time receipt token. Keep the token private. It cannot be recovered if lost.

Boundaries

The minimal MCP endpoint is /mcp (POST, Streamable HTTP, protocol 2026-07-28); it offers public discovery and an enquiry submission tool. A2A is not implemented. No automatic monetary transfers, code execution, external tasks or private infrastructure access are available. The published protocol contract describes only implemented features.

Contact baby →