Canonical Block Reference โ LLMFeed JSON
๐ฆ LLMFeed Canonical Block Reference
This document provides a centralized reference for the standard blocks used in LLMFeed files โ whether MCP, Export, Prompt, Credential, Pricing or others.
๐งฑ Common Top-Level Blocks
Block | Description | Required | Used in Feed Types |
---|---|---|---|
`feed_type` | Declares the type of feed (`mcp`, `export`, `prompt`, etc.) | โ Yes | All |
`metadata` | Describes the feedโs purpose, origin, title, and generation info | โ Yes | All |
`trust` | Optional trust object (signed_blocks, scope, certifier, hints) | โ ๏ธ Optional | All |
`signature` | Cryptographic signature block (hash, method, issuer) | โ ๏ธ Optional | All |
`certification` | Optional authority-issued certification object | โ ๏ธ Optional | All |
`intent` | Declares what the feed is meant to trigger or express | โ๏ธ Contextual | Prompt, MCP |
`audience` | Declares intended recipients: `llm`, `developer`, `agent_wrapper`, etc. | โ๏ธ Contextual | All |
`capabilities` | Lists functions or actions callable via API | โ๏ธ Optional | Capabilities |
`prompts` | List of triggerable phrases and related intents | โ๏ธ Optional | Prompt-index, MCP |
`pricing_models` | List of economic models and per-unit costs | โ๏ธ Optional | Pricing |
`data` | Content body (HTML, text, zip, files, session, etc.) | โ๏ธ Contextual | Export, Bundle, Session |
`agent_services` | Human interaction hooks (forms, booking, callbacks) | โ๏ธ Optional | MCP, Capabilities |
`session_state` | Used for agent context replay | โ๏ธ Optional | Session-feed |
๐ `trust` block
The trust
block governs which parts of the feed are verifiably trusted and optionally provides scope or hints.
Typical fields include:
json
"trust": {
"signed_blocks": ["feed_type", "metadata", "trust", "data"],
"scope": "public",
"certifier": "https://llmca.org",
"public_key_hint": "https://llmca.org/.well-known/public.pem",
"algorithm": "ed25519",
"hints": "critical context integrity"
}
๐ `signature` block
Used to cryptographically prove the authenticity of specific signed_blocks
.
json
"signature": {
"value": "abc123...",
"created_at": "2025-06-01T12:34:56Z"
}
๐๏ธ `certification` block
Issued by a trusted authority (like LLMCA), it certifies the whole feed or key parts of it.
json
"certification": {
"issuer": "https://llmca.org",
"cert_id": "llmca-2025-001",
"certified_blocks": ["feed_type", "metadata", "trust"],
"public_key_hint": "https://llmca.org/.well-known/public.pem"
}
๐ Related Specs
- `llmfeed.md` โ foundational rules
- `llmfeed_extensions_signatures.md`
- `llmfeed_feedtype_export.md`
๐ Notes
- Only
feed_type
andmetadata
are strictly required trust.signed_blocks
governs what is verifiably trustedsignature
andcertification
can co-exist- Unrecognized blocks should be namespaced
โก
Ready to Implement? Get AI-Powered Guidance
Reading docs manually takes time. Your AI can digest the complete LLMFeed specification and provide implementation guidance tailored to your needs.
๐ฏ
Quick Start
Essential concepts for immediate implementation
~22K tokens โข 30s analysis โข Core concepts
๐
Complete Mastery
Full specification with examples and edge cases
~140K tokens โข 2min analysis โข Everything
๐ก Works with Claude, ChatGPT, Geminiโก Instant implementation guidance๐ฏ Tailored to your specific needs