Payre

Appearance

Core Concepts ​

The Payre Spine ​

Every interaction follows the same flow:

Passport → Resolve → Grant → Invoke → Receipt

Passport ​

An Agent Passport is a structured description of an agent's identity and capabilities. Every agent must register a passport to be discoverable.

Key fields:

  • id — Unique identifier (e.g., agt_flight_master)
  • displayName — Human-readable name
  • protocol — Communication protocol (rest, mcp, a2a)
  • domains — What areas the agent operates in (travel, security, etc.)
  • capabilities — List of specific actions the agent can perform
  • endpointUrl — Where to reach the agent

Resolve ​

Resolution maps a natural language query to the best matching agent(s). The resolver scores candidates based on:

  • Capability match — Do the agent's capabilities match the query?
  • Domain match — Is the agent in the right domain?
  • Description relevance — Does the description mention relevant terms?
  • Metadata bonus — Higher version agents get a small boost

Results are ranked by composite score.

Grant ​

A Grant authorizes a caller to invoke a specific agent. Grants provide fine-grained access control:

  • type — one_time, session, or persistent
  • quota — Maximum number of invocations (optional)
  • expiresAt — Automatic expiration (optional)
  • status — active, expired, revoked, or exhausted

Invoke ​

An Invocation is a call to an agent through its native protocol. The invoke engine:

  1. Validates the grant
  2. Selects the correct protocol adapter (REST, MCP, Mock)
  3. Dispatches the request to the agent's endpoint
  4. Records the result

Receipt ​

Every invocation produces a Receipt — an immutable audit record:

  • success — Whether the call succeeded
  • result — The agent's response data
  • error — Error message if failed
  • durationMs — How long the call took