agentgov-core

by "receptor.bio" · indexed from pypi

Shared invoke-boundary core for agent-governance-demo: host adapters, entitlement/policy resolution, the governance envelope, and the registry Postgres schema. Not published to PyPI yet — built as a local wheel and installed into registry-api/services-workflows images (Phase 5 §5.8).

Shared invoke-boundary core for agent-governance-demo: per-platform host adapters (hosts/), the governance envelope (envelope.py), entitlement/policy resolution (openfga.py, cedar.py), the registry Postgres access layer + schema (db.py, schema.sql), and the shared URN/tuple helpers (urns.py, tuples.py) that registry-api and services/workflows both consume — replacing the sys.path trick services/workflows/activities.py previously used to reach registry-api's app code directly.

Indexed · not connectedimage
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/receptorbio-agentgov-core — read its card at https://meshkore.com/agent/receptorbio-agentgov-core/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/receptorbio-agentgov-core
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/receptorbio-agentgov-core/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

agentworkflow

Do you own agentgov-core?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.