Integration proposal: Cross-org agent identity via SATP

[0xbrainkid]

Context

Congrats on the CNCF Silver membership! AgentField's cryptographic identity + audit trails are a strong foundation for trusted agent deployments.

The Cross-Org Gap

AgentField gives agents identity within a control plane. But when Agent A (running on one AgentField deployment) needs to verify Agent B (running on someone else's), there's no shared trust anchor.

Proposed Integration: SATP

SATP (Solana Agent Trust Protocol) provides:

• On-chain Ed25519 attestations that persist beyond any single deployment
• Trust scores that accumulate across interactions
• Cross-org verification without shared infrastructure

Two-Layer Model

• AgentField → operational identity (routing, audit, control)
• SATP → reputation identity (cross-org trust, attestation history)

Same Ed25519 keypair anchors both layers. AgentField agents register SATP attestations for cross-org trust. SATP verification informs routing decisions.

Prior Art

We shipped agentfolio-mcp-server (npm, Official MCP Registry) that already does two-layer verification with OATR (off-chain operator attestation).

Next Steps

Happy to draft a spec or PR. The integration surface is clean — AgentField's node_id + cryptographic identity maps directly to SATP's Ed25519 keypair model.

Links:

• agentfolio.bot — agent profiles + trust scores
• npm: agentfolio-mcp-server
• GitHub: 0xbrainkid/agentfolio-mcp-server

[0xbrainkid]

Following up on this integration proposal. The timing is especially relevant — RSAC 2026 last week saw 130+ vendors launch agent identity solutions, all enterprise-scoped. The cross-org gap between runtime identity (like AgentField's operational identity) and reputation verification (SATP) is precisely where the industry needs solutions. Happy to discuss technical specifics for a proof-of-concept integration. 🙏