inco.org valid

Inco

Inco is a full-stack privacy layer for blockchains. It powers programmable confidentiality for smart contracts, protecting address and transaction details across payments, DeFi, onchain finance, gaming, governance, and more. Inco is not a new blockchain; it integrates with existing networks, similar to how TLS/SSL added encryption to the internet.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T08:46:29.117Z. Cached copy · Source on inco.org

# Inco

> Inco is a full-stack privacy layer for blockchains. It powers programmable confidentiality for smart contracts, protecting address and transaction details across payments, DeFi, onchain finance, gaming, governance, and more. Inco is not a new blockchain; it integrates with existing networks, similar to how TLS/SSL added encryption to the internet.

Developers build with Inco using familiar tooling: Solidity on EVM, Rust on SVM, with support for Hardhat, Foundry, Anchor, and standard wallets (MetaMask, Coinbase Wallet, Phantom, and others). The architecture is TEE-based, non-custodial, verifiable end-to-end, and post-quantum secure, with a force-exit path so users retain full control of their funds.

Inco Lightning is live on Base Sepolia testnet and on Solana Devnet (beta), with Base mainnet launching soon. 

## Products

- [Inco Lightning](https://www.inco.org/lightning): smart contract library for confidential payments, DeFi, gaming, governance, prediction markets, and identity, at the native speed of the host chain
- [Demos](https://experiences.inco.org/): interactive walkthroughs of Inco use cases

## Documentation

- [Docs home](https://docs.inco.org/): main entry point for builders
- [Introduction](https://docs.inco.org/introduction): overview of Inco for EVM developers
- [Quickstart](https://docs.inco.org/quickstart): build and deploy a confidential contract in minutes
- [Build a dApp](https://docs.inco.org/quickstart/build-a-dapp): scaffold a full-stack confidential dApp with create-inco-app
- [Library reference](https://docs.inco.org/quickstart/lib-reference): all functions exposed by the Inco library
- [Cheatcodes reference](https://docs.inco.org/quickstart/cheatcodes-reference): simulate the Inco environment in Solidity tests
- [Fees](https://docs.inco.org/quickstart/fees): which operations require fees and how they work
- [JavaScript SDK (incoJs)](https://docs.inco.org/js-sdk): interact with the Inco protocol from frontends and backends
- [Encrypting values](https://docs.inco.org/js-sdk/encryption): encrypt supported types (euint256, ebool, eaddress) with incoJS
- [NextJS starter](https://docs.inco.org/js-sdk/nextjs-starter): template for building dApps with Inco
- [Use IncoJS in an existing project](https://docs.inco.org/js-sdk/existing-project): drop incoJS into a JS/TS codebase
- [Architecture overview](https://docs.inco.org/architecture/overview): how Inco works under the hood
- [Components](https://docs.inco.org/architecture/components): protocol components and their roles
- [Decryption mechanisms](https://docs.inco.org/architecture/decryption-mechanisms): how encrypted state is revealed
- [Concepts guide](https://docs.inco.org/guide/intro): the core concepts to understand before building
- [Access control](https://docs.inco.org/guide/guide-access-control): programmable access control over encrypted data
- [Handles](https://docs.inco.org/guide/handles): unique identifiers for immutable encrypted values
- [Inputs](https:
…

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

Claim my listing on Agent Web Map for inco.org:
1. POST https://agentwebmap.com/v1/sites/inco.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://inco.org/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/inco.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/inco.org).
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.