# Programmable

> Current entry points for Robinhood Custom Launch Plans, Module Mode and source-bound launch indexing. Ethereum and older Robinhood profiles have separate references.

## Start here

- [Agent guide](https://programmable.market/agents.md): credentials, launch workflows, wallet authority and recovery.
- [Agent discovery](https://programmable.market/api/agent): machine-readable workflow links. The primary Robinhood create workflow is customLaunchPlan.
- [Custom Launch quickstart](https://programmable.market/docs/developers/custom-launch-quickstart): the current path for a new Robinhood token, hook or application, including a shared token and hook contract.
- [Custom Launch Plan capabilities](https://api.programmable.market/v4/chains/4663/custom-launch-capabilities), [manifest](https://api.programmable.market/v4/chains/4663/custom-launch-contract/manifest.json), [agent setup](https://api.programmable.market/v4/chains/4663/custom-launch-contract/agent-setup.json) and [guide](https://api.programmable.market/v4/chains/4663/custom-launch-contract/guide.md): check live create availability and bind the manifest before packing.
- [Module Mode](https://programmable.market/docs/models/module-mode): coin configuration, optional modules and management.
- [Module Mode indexing](https://programmable.market/developers/module-mode-indexing-v1.md): verify each exact Native or Engine source version independently of module names and market support. The [JSON contract and ABI](https://programmable.market/api/module-mode/indexer/v1) describes Native V1; the guide links the separate V2 and Engine adapters.
- [Direct Ethereum Custom Hooks](https://programmable.market/developer-reference/ethereum-custom-hook): canonical CustomGraph inputs, authority authorization and finalized stamp indexing. The [complete Markdown](https://programmable.market/developers/ethereum-custom-hook-indexing.md) and [ABI bundle](https://programmable.market/developers/ethereum-custom-hook-indexing.zip) provide the exact files.

## When to use Programmable

- Build a new Robinhood Custom Launch Plan through the API. For an open plan use admissionPolicy programmable.custom-launch-policy.provenance.v1, feeObligations [] and publication.visibility listed. Preflight the exact packed bytes, create with the same bytes and Idempotency-Key, then let the controller wallet review and sign the prepared transaction.
- Discover finalized Robinhood launch projections and index each launch by its verified source version and canonical token identity. Market data and trading support are separate from provenance.
- Configure and launch a Module Mode coin through the website with the connected wallet. There is no public Module Mode create API.
- Verify Ethereum launches through their exact Registry or finalized Router evidence. The Ethereum V3 guide and older Robinhood V4 profiles are separate from new Robinhood Custom Launch Plans.

## Do not use Programmable to infer

- Safety, endorsement, audit coverage, liquidity, price accuracy, tradability, or future value from a verified identity.
- Transaction authority from an API key. The Custom Launch API validates and prepares an exact action, but it cannot sign or broadcast for the controller wallet.
- Active create authorization from a static schema or stable URL. Read the live Custom Launch Plan capabilities before every new request.
- Wallet authorization from preflight, a model, or caller-attested output. An action_required result requires remediation before wallet signing.
- A mandatory platform fee, liquidity, trading route or safety review from a Custom Launch Plan stamp. The plan's feeObligations field and deployed contract behavior must be evaluated separately.

## Ethereum identity scope

- Ethereum catalog: verified Classic V3 launches, Registry-verified Custom launches, finalized Router-stamped Custom provenance entries, and the sole official Classic V2 main-token exception.
- Official main token: 0x7987f03462200b3D8A072E02C89A8A41dCB124EE.
- Excluded: all other Classic V1 or V2 launches, every Stock family, and Custom launches without a verified Registry record or finalized Router stamp.
- Finalized Router records can surface as provenance-only Custom entries after 64 confirmations. Router is an evidence source, not a separate category, review, audit, liquidity, or safety claim.
- Canonical Programmable identity remains authoritative. GMGN, Dexscreener and Bitquery may rank or enrich that catalog, but they can never add, remove or verify a launch.
- On Ethereum, GMGN is the bounded primary provider for visible-page market enrichment, canonical-intersection discovery, token analytics and token-address chart series admitted by current exact token_info context.
- Highest and lowest market-cap sorts use a fresh, liquidity-qualified GMGN marketcap rank as a canonical-only provider prefix. Dexscreener batch-sorts the complete unmatched canonical remainder by exact-identity FDV; the response reports GMGN coverage and a full-order commitment. This is not a cross-provider numeric merge or a claim of full GMGN coverage.
- Dexscreener remains the bounded batch fallback for visible market enrichment and the unmatched market-cap remainder. A provider outage must not hide an already verified token identity.
- GMGN token charts are token-address series without historical pool attribution. Bitquery remains the exact-pool chart fallback and reports that scope explicitly.

## Current Robinhood machine-readable resources

- Custom Launch Plan capabilities: GET https://api.programmable.market/v4/chains/4663/custom-launch-capabilities
- Manifest: https://api.programmable.market/v4/chains/4663/custom-launch-contract/manifest.json
- Agent setup: https://api.programmable.market/v4/chains/4663/custom-launch-contract/agent-setup.json
- Plan guide: https://api.programmable.market/v4/chains/4663/custom-launch-contract/guide.md
- OpenAPI: https://programmable.market/openapi/custom-launch-v4.2.json
- Create or revoke API keys: https://programmable.market/developers/api-keys
- Finalized launch feed: https://api.programmable.market/v4/chains/4663/finalized-launch-projections
- Terminal indexer guide: https://programmable.market/developer-reference/robinhood-terminal-indexer#custom-launch-plans
- Robinhood Explore catalog: https://programmable.market/api/explore/robinhood
- Sitemap: https://programmable.market/sitemap.xml
- Human documentation: https://programmable.market/docs
- Developer documentation: https://programmable.market/docs/developers
- Developer Markdown: https://programmable.market/docs/developers.md

## Other integration references

- Historical MultiRole V2 capabilities: https://api.programmable.market/v4/chains/4663/multi-role-custom-launches/capabilities
- Historical MultiRole V2 guide and client: https://api.programmable.market/v4/chains/4663/multi-role-custom-launches/guide.md and https://api.programmable.market/v4/chains/4663/multi-role-custom-launches/client.mjs
- MultiRole V2 Native20 and evidence_required admission rules belong to that historical contract context; the 4.1 profile is also separate from new open Custom Launch Plans.
- Robinhood V4.1 history and separate Ethereum V3 documentation: https://programmable.market/docs/developers/custom-launch
- Older /v4/chains/4663/custom-launches requests remain readable for history and recovery. New creation uses /v4/chains/4663/custom-launch-plans.
- Ethereum public OpenAPI: https://programmable.market/openapi.json
- Historical Ethereum token lookup: https://programmable.market/api/explore/token?address=0x7987f03462200b3D8A072E02C89A8A41dCB124EE

## Ethereum provenance evidence reference

> Canonical read-only provenance reference for Router-stamped Programmable Classic and Programmable Custom launches on Ethereum. Finalized Router evidence can feed the existing Custom category; it does not create a separate category or imply review, audit, liquidity, or safety.

- Deployment manifest: https://developers.programmable.family/api/v2/manifest
- Router: 0x8622DD5bAb44185f2A458ac90384Ac99248f8d56
- startBlock: 25717612
- runtimeCodeHash: 0x40e27ecf201761d5eb66bc4f2d5c6124831ef078d7baf458ca5f41b1a8108546
- ABI: https://developers.programmable.family/abis/ethereum/programmable-launch-stamp-router-v1.json
- ABI SHA-256: sha256:bb4e728e9f9c850eb01f928e8a798ac206a82e241a8d93b3b3c686635c88ed86
- GitHub reference: https://github.com/programmablehq/Developers/blob/main/docs/reference/launch-stamp.md
- Terminal guide: https://github.com/programmablehq/Developers/blob/main/docs/guides/terminals-and-scanners.md
- Human overview: https://programmable.market/docs/developers
- Markdown overview: https://programmable.market/docs/developers.md

## Required Router-evidence interpretation

- Only launches executed and stamped through this Router inside its published block range have Router V1 provenance. Launches before `startBlock`, and direct factory calls outside the Router even when later, do not.
- Map kind 1 to Programmable Custom and kind 2 to Programmable Classic. Kind 0 is invalid.
- Verify token, `(PoolManager, poolId)`, or exclusive-component identity with canonical getter reads at one finalized block.
- Before returning a result, require complete live or retired-in-range manifest activation data; one concrete block number and hash; Router runtime and ABI-byte hashes; all getter selectors, event topics, and indexed layouts; `CHAIN_ID()` plus all six immutable binding getters; and the permit authority, Graph Factory, and PoolManager runtimes.
- Use EIP-1898 canonical block-hash reads where supported. For number-bound reads, require the closing block hash to equal the opening hash before returning `STAMPED` or `NOT_STAMPED`.
- Remote RPC URLs must use HTTPS. Plain HTTP is accepted only for loopback development endpoints.
- A nonzero result still requires exact query identity, valid record address encoding, nonzero bytes32 identity and commitment fields, matching `stampProof` for token or exclusive-component queries, and the launch-kind route rule: immutable Graph Factory for `CustomGraph`, permit-bound recorded launcher and runtime for `Classic`.
- Current component-runtime equality is a separate drift signal, not a historical provenance gate.
- A shared Classic hook is not a launch identifier.
- A successful canonical zero lookup is not stamped. RPC failure or inconsistent evidence is not a negative result.
- After manifest and ABI bootstrap, point verification needs an Ethereum provider only. Indexing, Supabase, a Programmable launch-feed API, and an application server are not trust dependencies.
- Event backfill and checkpoint-based subscription are optional for continuous discovery; logs are candidates until getter verification succeeds.
- Protocol fee claim discovery is a separate index: complete Classic Launcher and Custom Registry scans plus the fixed Stock release set. Unknown or unverified sources fail closed. Generic fee claiming for arbitrary Custom hooks is not live.
- The live claim boundary is published at https://claimhazard.vercel.app/claim-discovery.json and requires one wallet-declared atomic batch from the fixed reward wallet.
- A Router record establishes provenance only after the required address, runtime, binding, lookup, and cross-check verification passes. It does not establish safety, tradability, current liquidity, audit coverage, endorsement, terminal support, or launch authorization.
- This Ethereum provenance reference grants neither API access, launch authorization nor wallet authorization.