veralang.dev valid
Vera
Vera is a statically typed, purely functional programming language designed for large language models to write. It uses typed slot references (`@T.n`) instead of variable names, requires contracts (preconditions, postconditions, effect declarations) on every function, and compiles to WebAssembly. Programs run at the command line via wasmtime or in the browser.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:04:55.517Z. Cached copy · Source on veralang.dev
# Vera
> Vera is a statically typed, purely functional programming language designed for large language models to write. It uses typed slot references (`@T.n`) instead of variable names, requires contracts (preconditions, postconditions, effect declarations) on every function, and compiles to WebAssembly. Programs run at the command line via wasmtime or in the browser.
Vera uses De Bruijn indexing for bindings: `@Int.0` is the most recent `Int` binding, `@Int.1` the one before. There are no variable names. Contracts are mandatory — every function must declare `requires(...)`, `ensures(...)`, and `effects(...)`, and every recursive function a `decreases(...)` measure or the `Diverge` effect. The Z3 SMT solver verifies contracts statically where possible; every contract is also compiled as a runtime check where code generation can express it, and most of what can be neither proved nor guarded is disclosed (#1695 tracks the contracts that are not). All side effects (IO, Http, HttpServer, State, Exceptions, Async, Inference, DB, Random, Diverge) are tracked in the type system via algebraic effects.
The reference compiler is written in Python; its releases are listed on [GitHub](https://github.com/aallan/vera/releases) and [PyPI](https://pypi.org/project/veralang/). Install the `veralang` distribution from PyPI, or use `pip install -e ".[dev]"` from the repository — the recommended route for agents, since it includes the examples, conformance programs and specification the language reference teaches from.
## Homepage
- [Vera](https://veralang.dev/index.md): Markdown companion to veralang.dev — project overview, thesis, design principles, key features, quick install, and links to the full documentation set.
## Language Reference
- [SKILL.md](https://veralang.dev/SKILL.md): Complete language reference — syntax, types, slot references, contracts, effects, built-in functions, common mistakes, and working examples. This is the primary document for writing Vera code.
## Quick Start
- [AGENTS.md](https://raw.githubusercontent.com/aallan/vera/main/AGENTS.md): Instructions for AI agents — workflow, commands, error handling, and essential rules for writing correct Vera.
- [FAQ](https://raw.githubusercontent.com/aallan/vera/main/FAQ.md): Design rationale — why no variable names, what gets verified, comparison to Dafny/Lean/Koka, research citations.
- [TOOLCHAIN.md](https://raw.githubusercontent.com/aallan/vera/main/TOOLCHAIN.md): The CLI cookbook — driving the toolchain to write, verify, test, run, and debug Vera, and the `builtins`/`effects`/`errors` introspection commands.
- [DE_BRUIJN.md](https://raw.githubusercontent.com/aallan/vera/main/DE_BRUIJN.md): Typed slot references in depth — worked examples and the commutative-operations trap.
- [ENVIRONMENT.md](https://raw.githubusercontent.com/aallan/vera/main/ENVIRONMENT.md): Every `VERA_*` environment variable — provider keys, runtime knobs, and debug flags.
- [KNOWN_ISSUES.md](https://raw.githubuserco
…
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 |
|---|---|---|---|---|---|---|---|
| rescript-lang.org | ReScript Documentation for LLMs | documentation Developer tools Documentation and reference | — | 50 | ✓ | ||
| averlang.dev | Aver | documentation Developer tools | — | 46 | ✓ | ✓ | |
| artscript.dev | ArtScript | documentation AI and machine learning AI agents and MCP +2 | US | 45 | ✓ | ✓ | |
| derw-lang.com | Derw | documentation Developer tools Documentation and reference | — | 46 | ✓ | ✓ | |
| imba.io | Imba | documentation Developer tools | NL | 50 | ✓ | ✓ | |
| factorcode.org | Factor | documentation Developer tools Documentation and reference | US | 56 | ✓ | ||
| gensx.com | GenSX | documentation Developer tools AI agents and MCP | US | 50 | ✓ | ✓ | |
| flix.dev | Flix | documentation Education Infrastructure +1 | DE | 46 | ✓ |
Machine-readable: GET /v1/resolve?q=veralang.dev · GET /v1/domain/veralang.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 veralang.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.
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 veralang.dev:
1. POST https://agentwebmap.com/v1/sites/veralang.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://veralang.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/veralang.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/veralang.dev).
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.