harmoniclabs.tech valid
Pebble
Pebble is a standalone smart-contract language for Cardano, targeting Untyped Plutus Core (UPLC). It compiles `contract` declarations (with optional `state` variants) into validators that fit the script-purpose dispatch model (`spend` / `mint` / `certify` / `withdraw` / `propose` / `vote`).
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T13:35:18.466Z. Cached copy · Source on harmoniclabs.tech
# Pebble
> Pebble is a standalone smart-contract language for Cardano, targeting Untyped Plutus Core (UPLC). It compiles `contract` declarations (with optional `state` variants) into validators that fit the script-purpose dispatch model (`spend` / `mint` / `certify` / `withdraw` / `propose` / `vote`).
This index points at the canonical reference pages. Each page is short, self-contained markdown.
## Language
- [Welcome to Pebble](/Welcome%20to%20Pebble): tagline, audience layering, entry points
- [Installation](/Installation): toolchain setup
- [Project Setup](/Project%20Setup): scaffolding a new project
- [Syntax / Top Level Statements](/onchain/Syntax/Top%20Level%20Statements): module-level declarations
- [Syntax / Block Statements](/onchain/Syntax/Block%20Statements): inside-function constructs
- [Syntax / Control Flow Statements](/onchain/Syntax/Control%20Flow%20Statements): `if`, `match`, `for`, `while`, `return`, `break`, `continue`, `assert`, `trace`, `fail`
- [Syntax / Namespaces](/onchain/Syntax/Namespaces): `using` and qualified access
- [Contract Statements](/onchain/Contract%20Statements): the `contract` declaration in full
- [State](/onchain/State): the `state` keyword (stateful UTxO contracts)
- [Builtin Values and Literals](/onchain/Builtin%20Values%20and%20Literals): integer/byte/string/array/struct literals, `context`, `fail`
- [Builtin Interfaces](/onchain/Builtin%20Interfaces): `ToData`, `Show`
## Prelude types
Every type available without an import, with operator and method-call surface.
- [int](/onchain/Prelude/Int): arbitrary-precision signed integers
- [bytes](/onchain/Prelude/Bytes): raw byte strings + `Hash28`/`Hash32`/`PolicyId`/`TokenName`/`PubKeyHash`/`ScriptHash`/`TxHash` aliases
- [string](/onchain/Prelude/String): UTF-8 text
- [bool](/onchain/Prelude/Boolean): truth values
- [data](/onchain/Prelude/Data): Plutus Data; five constructors (`Constr` / `Map` / `List` / `I` / `B`)
- [List\<T\>](/onchain/Prelude/List): linked list; O(n) indexing
- [Array\<T\>](/onchain/Prelude/Array): random-access counterpart of `List<T>`
- [LinearMap\<K, V\>](/onchain/Prelude/LinearMap): association-list "map"
- [Optional\<T\>](/onchain/Prelude/Optional): `Some{ value: T }` / `None{}`
- [Value](/onchain/Prelude/Value): native multi-asset bundle
## Standard library — `std`
Function-shaped equivalents of every method, plus crypto and low-level builtins.
- [std.crypto](/onchain/Standard%20Library/std.crypto): hashes (`sha2_256`, `sha3_256`, `blake2b_256`/`224`, `keccak_256`, `ripemd_160`), signature verifiers (Ed25519, ECDSA secp256k1, Schnorr secp256k1)
- [std.crypto.bls12_381](/onchain/Standard%20Library/std.crypto.bls12_381): G1/G2/MlResult pairing primitives
- [std.builtins](/onchain/Standard%20Library/std.builtins): Plutus Core builtins (arithmetic, bytestring, bitwise v3, encoding, data ctors/dtors, native value ops, polymorphic intrinsics `trace`/`ifThenElse`/`mkCons`/`chooseList`/`chooseData`)
- [std.list](/onchain/Standar
…
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 |
|---|---|---|---|---|---|---|---|
| veralang.dev | Vera | documentation AI and machine learning Developer tools | US | 45 | ✓ | ✓ | |
| moonbitlang.com | MoonBit Documentation | documentation Developer tools Documentation and reference | US | 52 | ✓ | ||
| rescript-lang.org | ReScript Documentation for LLMs | documentation Developer tools Documentation and reference | — | 50 | ✓ | ||
| openzeppelin.com | OpenZeppelin Docs | documentation Crypto and Web3 Developer tools | — | 61 | ✓ | ||
| odra.dev | Odra | documentation Developer tools Documentation and reference +1 | US | 47 | ✓ | ||
| derw-lang.com | Derw | documentation Developer tools Documentation and reference | — | 46 | ✓ | ✓ | |
| deployoor.dev | deployoor | documentation Developer tools | US | 46 | ✓ | ✓ | |
| tevm.sh | Tevm Node | interface Developer tools APIs and SDKs +1 | US | 45 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=harmoniclabs.tech · GET /v1/domain/harmoniclabs.tech · 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 harmoniclabs.tech, 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 harmoniclabs.tech:
1. POST https://agentwebmap.com/v1/sites/harmoniclabs.tech/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://harmoniclabs.tech/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/harmoniclabs.tech/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/harmoniclabs.tech).
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.