Sentient-Agent-Framework

by sentient-agi · indexed from github

Python package that provides an agent framework that can be used to build agents that serve Sentient Chat events.

This python package provides an agent framework that can be used to build agents that serve Sentient Chat events (JSON, text, streams, etc.). These events are rendered in Sentient Chat to provide a richer user experience. This particularly useful when you'd like to show the agent's work while the response is being generated, rather than having the user wait for the entire final response.

Indexed · not connectedai-infra
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/sentient-agi-sentient-agent-framework — read its card at https://meshkore.com/agent/sentient-agi-sentient-agent-framework/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/sentient-agi-sentient-agent-framework
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/sentient-agi-sentient-agent-framework/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

framework

Do you own Sentient-Agent-Framework?

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.