devfra.me valid
Devframe
Framework-neutral foundation for building devtools: one definition becomes a Web Standard handler, a CLI, a static report, an MCP server, or a hub dock.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T17:53:07.148Z. Cached copy · Source on devfra.me
# Devframe
> Framework-neutral foundation for building devtools: one definition becomes a Web Standard handler, a CLI, a static report, an MCP server, or a hub dock.
## Documentation
Every page below is available as raw markdown. Fetch any URL directly.
- [Landing page](https://devfra.me/raw/index.md): Overview of Devframe
- [Ecosystem](https://devfra.me/raw/ecosystem.md): Devtools, hosts and services built on Devframe by the community and the core team.
## Documentation Sets
- [Devframe Documentation](https://devfra.me/llms-full.txt): Complete Devframe documentation as plain markdown: guide, adapters, frameworks, add-ons, references, and the error reference.
## Guide
- [Guide](https://devfra.me/raw/guide.md)
- [Introduction](https://devfra.me/raw/guide.md): Devframe is a framework-neutral foundation for building a devtool once and running it everywhere - inside any host framework, as a standalone tool, or through a coding agent.
- [Getting Started](https://devfra.me/raw/guide/getting-started.md): Answer a few questions about the devtool you want to build and get a reading list tailored to it.
- [Tutorial: Build a Server Data Inspector](https://devfra.me/raw/guide/tutorial-server-data-inspector.md): Build a devtool that displays and queries live server-side data, then ship it as a hub dock entry, a static build, a standalone dev server, and a CLI.
- [Devframe Definition](https://devfra.me/raw/guide/devframe-definition.md): One defineDevframe call returns a portable DevframeDefinition any adapter consumes.
- [RPC](https://devfra.me/raw/guide/rpc.md): Type-safe, bidirectional RPC built on birpc, validated against any Standard Schema validator. Dev runs over WebSocket; build/SPA serves a pre-computed static dump.
- [Shared State](https://devfra.me/raw/guide/shared-state.md): Shared state is observable, immutable-by-default state synced between the node side and every RPC client, surviving reconnects: a new RPC client gets the snapshot.
- [Streaming](https://devfra.me/raw/guide/streaming.md): Streaming channels push chunk-style data from the node side to the browser side over the RPC socket.
- [Client Assets](https://devfra.me/raw/guide/client-assets.md): A devframe's UI is a built SPA; clientAssets says where it lives: a local directory or published npm package.
- [Scoped Context](https://devfra.me/raw/guide/scoped-context.md): A scoped context is a namespaced view of the context: it auto-prefixes every RPC id, shared-state key, and streaming channel with your tool's id, and adds a typed, persisted settings store, used from a single tool's code.
- [JSON-Render](https://devfra.me/raw/guide/json-render.md): JSON-render describes a UI as data: a serializable component spec any frontend renders. Opt-in: a plain devframe pulls zero JSON-render dependencies. Two packages:
- [Structured Diagnostics](https://devfra.me/raw/guide/diagnostics.md): ctx.diagnostics is a thin layer over nostics for author-defined coded diagnostics, each with a stable code
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| webflow.com | Webflow Developer Documentation | interface Developer tools APIs and SDKs | US | 71 | ✓ | ✓ | |
| dashfy.dev | Dashfy | documentation Developer tools | US | 45 | ✓ | ✓ | |
| substreams.dev | Substreams | documentation Data and analytics Developer tools | US | 46 | ✓ | ✓ | |
| openreplay.com | OpenReplay | documentation Data and analytics Developer tools +2 | — | 63 | ✓ | ✓ | |
| solidrpc.io | SolidRPC | interface APIs and SDKs Infrastructure +1 | US | 47 | ✓ | ||
| denext.dev | denext | interface Developer tools APIs and SDKs | — | 45 | ✓ | ✓ | |
| agent-native.com | Agent-Native | interface AI and machine learning Open source projects +2 | — | 56 | ✓ | ✓ | |
| json-render.dev | json-render | documentation AI and machine learning Developer tools | US | 46 | ✓ |
Machine-readable: GET /v1/resolve?q=devfra.me · GET /v1/domain/devfra.me · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage devfra.me, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for devfra.me:
1. POST https://agentwebmap.com/v1/sites/devfra.me/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://devfra.me/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/devfra.me/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/devfra.me).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.