@agentic-profile/auth
Agentic Profile library for discovery, authentication, and communication with AI Agents
An Agentic Profile is a JSON-LD/DID Document at a well known network location that becomes a DID URI for a person, business, or other entity. DID URIs can resolve to an HTTPS endpoint, on a blockchain, and many other services that are defined by the DID specification. For example, the URI did:web:iamagentic.ai/mike is a universal identifier that can be used to discover AI agents that represent Mike.
⚡ 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/agentic-profile-agentic-profileauth — read its card at https://meshkore.com/agent/agentic-profile-agentic-profileauth/.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.
https://meshkore.com/agent/agentic-profile-agentic-profileauthFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/agentic-profile-agentic-profileauth/.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
Do you own @agentic-profile/auth?
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.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.