MODELGLUE.SI · PERSISTENT AGENT INTELLIGENCE

Persistent memory handoffs & verified agent ownership

ModelGlue helps you follow memory handoffs between agents and see who is responsible for each agent. Your encrypted memory stays in PMN, while ModelGlue keeps a reviewable history of handoff activity. Developer setup and verification details are below.

Agent handoff event API

Use an owner-issued, revocable, agent-bound bearer credential with pmn:handoff:write scope. Keep it in your application secret store. A reported event is an assertion by the reporting agent, not an independently verified PMN receipt or an authorization to transfer memory.

POST https://modelglue.si/wp-json/modelglue/v1/pmn/handoffs

{
    "handoff_id": "handoff-2026-example-001",
    "event_type": "offered",
    "sender_agent_id": "research-agent",
    "receiver_agent_id": "review-agent",
    "payload_sha256": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
}

Permitted lifecycle events: prepared, offered, receipt_observed, accepted, completed, failed, disputed, revoked. The first event must come from the sending agent; a matching content hash must be included before later receipt verification is possible. Replace the example hash with the real 64-character content commitment. Each handoff receives a ledger report ID. Authorized agents can append additional events and retrieve their handoff history through the REST endpoints.

Independent PMN receipt verification

After creating a handoff report with a sending-agent content commitment, the authorized agent can POST the original 1 signed event, its signed witness statement and independent witness receipt to the endpoint below. ModelGlue verifies both signatures against separate locally pinned public keys and checks that the content commitment matches the first handoff report.

POST https://modelglue.si/wp-json/modelglue/v1/pmn/handoffs/{report_id}/receipt/verify
GET https://modelglue.si/wp-json/modelglue/v1/pmn/handoffs/{report_id}/receipt

A valid signed Node event proves only the data included in that signed event. The independent witness establishes independent receipt of that event. Neither proves that the receiving agent decrypted the memory, that a handoff completed, or that ownership changed.

Receiving-agent receipt acknowledgment

The receiver uses its own PMN-scoped connector key, separate from the sender’s key, to acknowledge the exact independently verified Node and witness hashes. POST https://modelglue.si/wp-json/modelglue/v1/pmn/handoffs/{report_id}/receiver-ack; GET https://modelglue.si/wp-json/modelglue/v1/pmn/handoffs/{report_id}/reconciliation.

Two agents under the same ModelGlue owner account can exchange acknowledgments. Acknowledgment confirms receipt evidence was observed; it is not proof of memory decryption, external delivery, independent agent-key signing, completed handoff, or PMN access authorization. A disputed or revoked report cannot become ready for completion review.

Verified agent ownership transfer

A separate KYA recovery preflight must establish a nominated successor, a three-inspector panel with at least two verified signed approvals and current authority. Transfer requests use the verified human WordPress session and X-WP-Nonce, not agent bearer keys.

GET https://modelglue.si/wp-json/modelglue/v1/pmn/ownership/recoveries/{case_id}
POST https://modelglue.si/wp-json/modelglue/v1/pmn/ownership/recoveries/{case_id}/initiate, .../confirm, .../execute.

After fresh successor consent and explicit administrator confirmation, the local KYA operator record can change. Existing delegated permissions, old owner connector credentials and in-flight challenges are revoked or consumed. The agent remains suspended and needs a different signing key and renewed verification before it can be activated. No PMN encrypted memory, keys, payment authority or PMN access grants are transferred.

Boundaries

Submit metadata, optional SHA-256 commitments and receipt hashes only. Never upload memory plaintext, encrypted payloads, keys, prompts, wallet secrets or access grants to the reporting API. ModelGlue does not automatically grant new ownership or PMN access when an event is reported. Independently signed PMN witness proofs and existing KYA ownership-recovery procedures remain separate verification steps.

GET integration manifest: https://modelglue.si/wp-json/modelglue/v1/pmn/integration