Skip to content
Universal Manifest

For Agents

This page is the human-readable companion to llms.txt and /.well-known/universal-manifest.json. If you are an external agent, start here instead of inferring the project structure from navigation chrome or browser bundles.

Section titled “Recommended Next Pages”

Start Order

Section titled “Start Order”
  1. Fetch /.well-known/universal-manifest.json.
  2. Fetch /llms.txt.
  3. Read About -> Agent Briefing.
  4. Read Getting Started -> Build Your Own Implementation.
  5. Read Reference -> Resolver API.
  6. If you need live runtime contract details, fetch https://myum.net/.well-known/myum-resolver.json and https://myum.net/openapi.json.

Domain Split

Section titled “Domain Split”
  • universalmanifest.net is the standards, documentation, discovery, and tooling host.
  • myum.net is the runtime UMID resolver host.
  • Treat these as complementary but different surfaces. The standards host explains and publishes the protocol. The runtime host resolves UMIDs.

Machine-Readable Entry Points

Section titled “Machine-Readable Entry Points”

Public Tool Surfaces

Section titled “Public Tool Surfaces”

Interaction Posture

Section titled “Interaction Posture”
  • These public surfaces are read-mostly.
  • universalmanifest.net and myum.net do not currently expose a public A2A task API.
  • There is no public agent task-claiming flow on these hosts.
  • There is no public MCP server on these hosts.
  • A public skill.md is intentionally deferred. The canonical discovery path is llms.txt plus the well-known descriptors.

Verification Guidance

Section titled “Verification Guidance”
  • Treat the versioned schema and JSON-LD context URLs under /ns/universal-manifest/ as the canonical artifact layer.
  • Use the fixture and sandbox catalogs instead of scraping UI JavaScript for available public examples.
  • Use the resolver descriptor and OpenAPI document for runtime contract behavior.
  • Use External Agent Onboarding when you need the recommended order for understanding, implementation, or runtime verification tasks.
  • Check the Changelog before claiming support for newly added features or routes.

Security

Section titled “Security”
  • Report vulnerabilities through the contact listed in /.well-known/security.txt.
  • Do not open public issues for undisclosed security problems.