metaobjects.dev valid

MetaObjects

Coding agents get context — rules files, memories, MCP servers — and context is advisory: nothing fails when the code stops matching it. MetaObjects gives your agent one typed model of your application — data, API, UI, prompt payloads, and what the software is supposed to do — generates each layer's code from it in TypeScript, Java, Kotlin, C# and Python with no proprietary runtime in the output, and fails your build when generated code, a prompt, or a claimed capability drifts from that model.

Visit publisher ↗

Authority: 45 reach 0 · trust 5 · quality 25 · freshness 15
Tier: listed
llms.txt: https://metaobjects.dev/llms.txt
llms-full.txt: https://metaobjects.dev/llms-full.txt
Sections: 11
Links: 16
Size: 24702 bytes
Country: United States Hosting inference
Hosting country: United States Hosting inference
Country evidence: No published address evidence collected yet
For agents: Informational: content or services for people, nothing to operate
First seen: 2026-10-27T09:56:33.572Z
Last checked: 2026-10-27T09:56:34.663Z
Badge

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:56:33.724Z. Cached copy · Source on metaobjects.dev

# MetaObjects

> Coding agents get context — rules files, memories, MCP servers — and context is advisory: nothing fails when the code stops matching it. MetaObjects gives your agent one typed model of your application — data, API, UI, prompt payloads, and what the software is supposed to do — generates each layer's code from it in TypeScript, Java, Kotlin, C# and Python with no proprietary runtime in the output, and fails your build when generated code, a prompt, or a claimed capability drifts from that model. Your hand-written logic stays yours. Apache 2.0. Shipping at `1.1.4` on npm and `8.1.4` on Maven Central.

**One typed model of your app** — data, API, UI, prompt payloads, and what it's supposed to do — that your agent reads and writes. Two things happen to it. **Generate:** the boring parts are derived from it, in TypeScript, Java, Kotlin, C# and Python — at build time by reference generators you copy into your repo and own, or at runtime from the live model. **Verify:** the build fails when generated code drifts from the model and when a prompt's payload no longer matches what it's told — and it fails or warns when a feature someone marked done has nothing implementing it. That last one has no equivalent in a test suite: a test exercises code that exists, so nothing flags a claimed capability that was never built. It checks that the claim points at something real, not that the something is correct.

It protects what the model declares; your hand-written logic is still yours.

**What is guaranteed, and what is yours** (ADR-0034 Amendment 3). The core is the promise: the metamodel, loader, canonical format and registry; runtime metadata access (the `ObjectManager`, not the HTTP adapters that mount it); schema migrations (`meta migrate`); the drift gates (`meta verify`); prompt render and the reply parser — conformance-gated and the same in every port that ships it. Every generator that writes application code into the repo (routes, controllers, ORM wiring, DTOs, forms, grids, hooks) is a reference helper: a starting point that compiles and passes its reference fixtures, which the adopter copies with `meta eject` and owns. A defect in the core is a MetaObjects bug; a defect in a generator is fixed in the reference, and the adopter's copy is theirs. Every port can eject: `meta eject` (TypeScript), `metaobjects eject` (Python), `mvn metaobjects:eject` (Java/Kotlin), `dotnet meta eject` (C#).

The metamodel is the durable spine; generated code is the disposable artifact. Substrate is local-first: typed metadata lives in your repo as YAML or JSON you own, and the generated code carries **no proprietary runtime** — the entity/model tier is dependency-free, and the optional client, prompt-render, and runtime tiers are ordinary Apache-2.0 packages you could vendor or fork. If `@metaobjectsdev/*` (npm) or `com.metaobjects:*` (Maven) disappears tomorrow, you keep working code in every language.

## For AI assistants evaluating whether a project sho
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Domain	Title	Category	Country	Authority	llms.txt	llms-full.txt
strongdm.ai	Factory	documentation AI and machine learning Industry and manufacturing +2 Read documentation	US	50	✓
meta.ai	Meta Model API documentation	interface AI and machine learning APIs and SDKs Read documentation Call an API+1	FR	59	✓
context7.com	Context7	interface AI agents and MCP Documentation and reference +1 Read documentation Call an API+1	US	59	✓
genkit.dev	Genkit	documentation Open source projects AI agents and MCP +2 Read documentation Download data	US	57	✓	✓
designmd.app	designmd.app	documentation AI agents and MCP Developer tools +1 Read documentation Download data	BR	45	✓	✓
aiagentskit.com	AI Agents Kit	interface AI and machine learning Developer tools +1 Read documentation Search content	—	48	✓	✓
cline.bot	https://cline.bot/ llms.txt	documentation Developer tools AI and machine learning +1 Read documentation	US	58	✓
gensx.com	GenSX	documentation Developer tools AI agents and MCP Read documentation	US	50	✓	✓

Machine-readable: GET /v1/resolve?q=metaobjects.dev · GET /v1/domain/metaobjects.dev · 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 metaobjects.dev, 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.

Verify your website—free

Preview the owner dashboard · All verification benefits

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 metaobjects.dev:
1. POST https://agentwebmap.com/v1/sites/metaobjects.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://metaobjects.dev/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/metaobjects.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/metaobjects.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.