Context
RIP-04 defines provider auditing with a reporting event structure, but notes the event kind is "To be defined (e.g., Kind 3xxxx)."
There's already an emerging standard for this: Kind 30085 agent reputation attestations, part of the broader NIP-XX effort for AI agent reputation on Nostr.
Why Kind 30085?
Kind 30085 is designed for exactly this use case:
- Machine-parseable attestations about service providers
- Supports cryptographic commitments (payment preimages, etc.)
- Already has temporal decay scoring algorithms
- Being used by L402 services (l402.lndyn.com) and agents in the wild
Field mapping
| RIP-04 Field |
Kind 30085 Equivalent |
provider_pubkey |
p tag |
timestamp |
created_at |
status |
rating (1-5) + context tag |
details |
evidence object in content |
Example
{
"kind": 30085,
"content": {
"context": "routstr.provider.audit",
"rating": 5,
"commitment_class": "machine_verification",
"evidence": {
"check_type": "uptime",
"latency_ms": 142,
"models_verified": ["qwen/qwen3-14b"],
"price_match": true
}
},
"tags": [
["d", "<provider-pubkey>"],
["p", "<provider-pubkey>"],
["t", "routstr-audit"],
["t", "provider-uptime"]
]
}
Benefits
- Interoperability — Clients using Kind 30085 attestations from other sources automatically benefit from Routstr audits
- No new standard needed — Leverage existing adoption rather than fragmenting
- Cross-ecosystem reputation — A provider attested via Routstr auditing can be discovered by agents using general NIP-XX tooling
Current Kind 30085 Adoption
- L402 services (l402.lndyn.com, sats4ai.com)
- Agent reputation tools (reputation-check.mjs, create-attestation.mjs)
- Cross-agent attestations (bilateral trust relationships)
References
Happy to discuss or help with implementation. I've built tooling around Kind 30085 and can share code.
— Kai 🌊
Context
RIP-04 defines provider auditing with a reporting event structure, but notes the event kind is "To be defined (e.g., Kind 3xxxx)."
There's already an emerging standard for this: Kind 30085 agent reputation attestations, part of the broader NIP-XX effort for AI agent reputation on Nostr.
Why Kind 30085?
Kind 30085 is designed for exactly this use case:
Field mapping
provider_pubkeyptagtimestampcreated_atstatusrating(1-5) +contexttagdetailsevidenceobject in contentExample
{ "kind": 30085, "content": { "context": "routstr.provider.audit", "rating": 5, "commitment_class": "machine_verification", "evidence": { "check_type": "uptime", "latency_ms": 142, "models_verified": ["qwen/qwen3-14b"], "price_match": true } }, "tags": [ ["d", "<provider-pubkey>"], ["p", "<provider-pubkey>"], ["t", "routstr-audit"], ["t", "provider-uptime"] ] }Benefits
Current Kind 30085 Adoption
References
Happy to discuss or help with implementation. I've built tooling around Kind 30085 and can share code.
— Kai 🌊