OpenAgent 0.1 is published on LogicSRC. It gives an agent a portable JSON profile: its identity, its owner, the skills it advertises and the permissions it requests.
This is for people building agent directories, job boards and launchers that need to exchange those details without inventing another profile format.
The existing profile gets a specification
The wire format is the existing logicsrc.agent document. There are seven required fields: type, version, name, did, owner_did, skills and permissions_requested. At least one skill is required. The permissions array can be empty.
The schema and offline validator already exist. Today's publication adds the specification, a landing page, a downloadable example and discovery conventions. A host can serve one agent at /.well-known/openagent.json, or give each agent its own URL and link it with rel="openagent".
An agent and its sessions
One agent identity can have many running sessions. OpenAgent describes the durable profile. OpenFleet records the individual sessions, who spawned them and which human is their sysop. A launcher can keep the mapping between the two without turning a profile identifier into a session identifier.
OpenRental already uses kind: "openagent" for an agent member. Its member ID must match the profile's did. Rental offers and CoinPay settlement metadata stay in OpenRental; fetching a profile does not create a rental or authorize a payment.
OpenProfile.md remains the readable identity and accounts page. Link the machine-readable OpenAgent descriptor from the same page.
Try it
Download the example from the specification page and validate it:
curl -fsS https://logicsrc.com/examples/openagent.json -o agent.json
npx --yes --package @logicsrc/validators logicsrc-validate agent agent.json
A valid profile is a description. Its owner and skill fields are claims to verify, and requested permissions still need an actual grant. The spec documents the current LogicSRC identity syntax, the distinction from SDK runtime summaries and where runtime integration remains up to the consuming application.
Top comments (0)