~/ domain/averlang.dev.mdTHE AGENT-READABLE WEB

averlang.dev valid

Aver

Aver is a statically typed language for a world where code is cheap to generate and expensive to trust. It is optimized for the person who reviews the code.

Visit publisher ↗

For agents: Aver: a statically typed programming language built for reviewing AI-generated code, with a playground and toolchain reference (run, verify, audit, format).

statically typed languageprogramming languagecode verificationllms-full.txtcode review

Authority
46 reach 0 · trust 6 · quality 25 · freshness 15
Tier
listed
llms.txt
https://averlang.dev/llms.txt
llms-full.txt
https://averlang.dev/llms-full.txt
Sections
4
Links
14
Size
50935 bytes
Registered
2026-04-10
Country
— Publisher location unknown; CDN address excluded
Country evidence
No published address evidence collected yet
Categories
Developer tools
For agents
Documentation: developer or product docs worth reading, nothing to call
Inferred actions
Read documentation About these labels
Audience
developers · agents can: read docs · en
First seen
2026-10-23T23:11:46.263Z
Last checked
2026-10-23T23:11:46.479Z
Badge
Agent Web Map badge for averlang.dev

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T23:11:46.268Z. Cached copy · Source on averlang.dev

# Aver

> Aver is a statically typed language for a world where code is cheap to generate and expensive to trust. It is optimized for the person who reviews the code.

- Website: [averlang.dev](https://averlang.dev)
- Playground: [averlang.dev/playground](https://averlang.dev/playground/)
- GitHub: [jasisz/aver](https://github.com/jasisz/aver)
- crates.io: [aver-lang](https://crates.io/crates/aver-lang)
- License: MIT
- Written in: Rust
- Backends: bytecode VM, Rust codegen, WASM, Lean 4 proof export

## Before you write Aver

If you read only one section, read this one.

- Files end with `.av`, not `.aver`
- Each file starts with exactly one `module <Name>` declaration
- Module metadata uses `intent =` and `exposes [...]`
- Bindings are `name = expr` or `name: Type = expr`. There is no `let`, `val` or `var`
- Constructors are always qualified: `Result.Ok`, `Result.Err`, `Option.Some`, `Option.None`
- There is no `if` / `else`; use `match`
- **Match arm bodies must start on the same line as `->`. This is the most common error.** Move longer logic into a helper function
- Functions do not have type parameters. Write `fn sum(xs: List<Int>) -> Int`, never `fn sum<T>(xs: List<T>) -> T`
- Effects are explicit: `! [Console.print]`, `! [Http.get]`
- Pure functions get `verify` blocks placed right next to them
- Classified effectful fns (Random, Disk, Http, Tcp one-shot, Time, Console.readLine, Terminal non-modal, all output) get `verify fn trace` with `given` stubs. Unclassified ambient, session and modal flows go through record/replay
- Parse integers with `Int.fromString`, which returns `Result<Int, String>`
- Convert unsigned integers to fixed-width protocol bytes with `Int.toBigEndian(value, width)` or `Int.toLittleEndian(value, width)`; both return `Result<Bytes, String>` unless both literal arguments prove the call cannot fail. Decode total `Bytes` values with `Int.fromBigEndian` / `Int.fromLittleEndian`
- `Console.readLine()` returns `Result<String, String>`, not a plain `String`

## Minimal correct file

```aver
module Hello
    intent = "Tiny intro module."
    exposes [greet, main]
    effects [Console.print]

fn greet(name: String) -> String
    ? "Builds a greeting."
    "Hello, {name}!"

verify greet
    greet("Aver") => "Hello, Aver!"

fn main() -> Unit
    ? "Entry point."
    ! [Console.print]
    Console.print(greet("world"))
```

The basic pattern:

- a pure function
- a `verify` block directly below it
- an effectful `main`
- a module-level `effects [...]` boundary that names every effect any function in the module uses (since 0.13)
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

DomainTitleCategoryCountryAuthorityllms.txtllms-full.txtSave
0state.com 0state documentation Open source projects AI agents and MCP +1 — 61 ✓
docker.com Docker Documentation documentation DevOps and observability Developer tools +1 US 75 ✓ ✓
atlassian.com Atlassian documentation Developer tools Productivity +1 — 74 ✓ ✓
getbootstrap.com Bootstrap documentation Open source projects Developer tools — 74 ✓ ✓
launchdarkly.com LaunchDarkly Documentation documentation DevOps and observability Developer tools CA 74 ✓ ✓
claude.com Claude Code Docs documentation Developer tools AI and machine learning +1 US 73 ✓ ✓
chatgpt.com Codex documentation Developer tools AI and machine learning — 72 ✓ ✓
gitee.com Gitee documentation Developer tools Productivity +1 CN 72 ✓ ✓

Machine-readable: GET /v1/resolve?q=averlang.dev · GET /v1/domain/averlang.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 averlang.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 averlang.dev:
1. POST https://agentwebmap.com/v1/sites/averlang.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://averlang.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/averlang.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/averlang.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.

agent web map / a clearer way in.API & MCP · Contact