Skip to content

Add NIP-AE: Agents#2220

Open
pablof7z wants to merge 4 commits intomasterfrom
agents
Open

Add NIP-AE: Agents#2220
pablof7z wants to merge 4 commits intomasterfrom
agents

Conversation

@pablof7z
Copy link
Member

@pablof7z pablof7z commented Feb 12, 2026

This PR adds some of the kinds I'm using in TENEX, it defines everything needed to instantiate an agent: agent definition, agent lessons and attribution.

Read here

Agent definitions can now reference NIP-94 file metadata events (kind 1063)
via e-tags. Execution platforms MAY provide access to these files.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@qingfeng
Copy link

Hey @pablof7z — this is great work. We just submitted NIP-AC (#2228) which defines 5 kinds for DVM agent coordination (heartbeat, job reviews, data escrow, workflow chains, competitive swarms).

I think NIP-AE and NIP-AC are naturally complementary:

  • NIP-AE = agent identity layer (what an agent is — definition, lessons, attribution)
  • NIP-AC = agent runtime layer (what agents do together — liveness, jobs, reputation)

A concrete integration point: an agent defined via Kind 4199 could publish Kind 30333 heartbeats to advertise which NIP-90 kinds it supports and its current capacity. The kinds tag in the heartbeat maps directly to the capabilities declared in the agent definition.

Would be interested to hear your thoughts on how these could reference each other. Our reference implementation is 2020117 — all 5 kinds are live at 2020117.xyz.

- d tag: agent slug for grouping versions from same author
- content: markdown-formatted extended description
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants