]> Ajna.inc

vinay@ajna.inc

Verid.id

dave@verid.id

ART well-known, link-relation, automation, agents, workflows, MCP This document registers a Well-Known URI, /.well-known/awp.json, and a companion Link Relation Type, awp. The resource exposes a small, machine-readable description of common website workflows (states, actions, and resulting events) so automated agents can act predictably without scraping. The format is JSON and intentionally minimal. Status information for this document may be found at . Source for this draft and an issue tracker can be found at .

Introduction Automation on the Web often relies on brittle scraping. Many sites already publish machine metadata (e.g., OpenAPI descriptions, sitemaps). This document defines a single optional entry point — a Well-Known resource — that advertises a compact, typed map of site workflows. Agents can use it to perform tasks deterministically (e.g., sign in, search, checkout). This document registers: the Well-Known URI: /.well-known/awp.json, and the Link Relation Type: awp. The resource is read-only and does not alter authorization; normal Web security controls continue to apply.

The AWP Resource An origin MAY expose a JSON resource at: GET /.well-known/awp.json Content-Type: application/awp+json The document contains: version — semantic version (required), initial — the starting state (required), states — a map of state → allowed action names (required), transitions — event-driven edges (from, event, to) (required), actions — named HTTP operations with form bindings (required), schemas — JSON Schema 2020-12 objects referenced by expects/produces (required), site — site metadata with name and baseUrl (required), template_id — unique identifier (optional), title — human-readable name (optional), description — template description (optional), openapi — link to OpenAPI spec (optional), policies — rate limiting and other policies (optional). A minimal example follows:

Servers MAY use RFC 6570 URI Templates in form.target (e.g., /api/search{?q,limit,offset}). API errors SHOULD use RFC 9457 Problem Details to allow deterministic branching by clients.

Discovery via Link Relation Origins SHOULD advertise the resource with: Link: </.well-known/awp.json>; rel="awp" The awp relation identifies the AWP manifest for the current origin.

Security Considerations The manifest is advisory; authentication and authorization remain unchanged. Do not place secrets or user-specific data in the manifest. Consider cache lifetimes so changes propagate appropriately. Implement normal rate-limiting/abuse controls on operational endpoints referenced by the manifest. Cross-origin access is governed by existing Web mechanisms (e.g., CORS).

IANA Considerations

Well-Known URI Registration IANA is requested to register the following in the “Well-Known URIs” registry: URI Suffix: awp.json Change Controller: IETF Specification Document: This document, Section 2 Status: permanent Related Information: JSON manifest describing site workflows for automated agents.

Link Relation Type Registration IANA is requested to register the following in the “Link Relation Types” registry: Relation Name: awp Description: Identifies the Agent Workflow Protocol (AWP) manifest for this origin. Reference: This document, Section 3

References RFC 8615 — Well-Known URIs RFC 8288 — Web Linking RFC 6570 — URI Templates RFC 9457 — Problem Details for HTTP APIs JSON Schema 2020-12 — Core & Validation