> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/developers/developers.md).

# Developer overview

Build on the same on-chain policy that the Bloxchain Platform enforces, using the open-source Bloxchain Protocol and its TypeScript SDK (`@bloxchain/sdk`).

**You need:** Node.js, an RPC endpoint on Sepolia, a wallet key for writes

## Who these pages are for

The documentation serves four audiences. This section is the third.

| Audience                                                                | Start here                                                                                                      |
| ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| Individual users operating the Platform                                 | [Your first smart account](/get-started/quickstart.md)                                                          |
| Organizations governing a shared account                                | [Organization governance](/guides/organization-governance.md)                                                   |
| **Builders and developers** using the Protocol in their own application | this section, then [Configure an account programmatically](/developers/sdk-setup/configure-programmatically.md) |
| AI agents and agent builders preparing work a person approves           | [For AI agents](/developers/for-ai-agents.md) and [Agent-assisted requests](/guides/agent-assisted-requests.md) |

## What you can build

A Bloxchain smart account is a contract you own. It holds assets and performs actions only through governed requests: a request is posted or signed, waits or collects approvals according to rules stored in the account, and only then executes. The Platform at bloxchain.app is one client of that contract. The SDK is another. Both talk to the same address and neither can bypass the policy on chain.

That gives you four practical options. You can **automate** an account your team operates in the Platform, for example a service that submits signed approvals with a Broadcaster key, or a monitor that watches request status. You can **deploy your own accounts** from the Protocol at the pinned release, on the 15 supported networks, and then import them into the Platform or operate them entirely from code. You can **configure accounts from code** rather than by clicking: register actions, create roles, assign each step of an execution path, grant gates and manage allowlists in signed batches. See [Configure an account programmatically](/developers/sdk-setup/configure-programmatically.md). Or you can **embed the policy layer** in your own product, with the Protocol contracts as the source of truth.

The Protocol core is audited; see [Audit status](/security/audit-status.md) for the scope and [Security](/security/security.md) for the model, the known limits and how to report a problem. Official deployments are live on the 15 supported networks, in the Platform and in the Protocol, and [Supported networks](/introduction/supported-networks.md) tracks the chains as they open. Maturity is **Alpha · Local-first**.

## Pages in this section

| Page                                                                                         | What it covers                                                                  |
| -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| [Integration surfaces](/developers/integration-surfaces.md)                                  | Platform, SDK and Protocol compared, how to choose one, and how to combine them |
| [SDK setup and authentication](/developers/sdk-setup.md)                                     | Install, pin versions, clients, keys, environment variables                     |
| [SDK core patterns](/developers/sdk-setup/sdk-core-patterns.md)                              | Reads, the three execution paths, statuses, errors, retries, worked examples    |
| [Configure an account programmatically](/developers/sdk-setup/configure-programmatically.md) | Script actions, roles, permissions, gates and allowlists                        |
| [Deploy the Protocol](/developers/deployment.md)                                             | Clone and deploy at the pinned release; immutable clones versus custom proxies  |
| [Production readiness](/developers/deployment/production-readiness.md)                       | Checklist before moving real value, plus recovery planning                      |
| [For AI agents](/developers/for-ai-agents.md)                                                | llms.txt, MCP, canonical sources, copy-paste prompt templates                   |

## Prerequisites

* Node.js 18.20 or later to run the SDK; Node.js 22.12 or later to work inside the Protocol repository.
* An RPC URL for Sepolia (chain 11155111). The SDK works with any EVM RPC; you pay gas from your own wallet.
* A funded Sepolia wallet for writes. Reads need no key.
* Basic familiarity with viem, which the SDK uses for clients and signing.

## Where to start

* New to the SDK: [Developer quickstart](/get-started/developer-quickstart.md), then [SDK setup and authentication](/developers/sdk-setup.md).
* Need the reference: [Protocol documentation](/protocol-reference/protocol.md), synced from the Protocol repository, including the [API reference](/protocol-reference/api-reference.md) and [Getting started](/protocol-reference/getting-started.md).
* Want to understand the lifecycle first: [How governed operations work](/introduction/how-it-works.md).
* Setting up accounts rather than sending transactions: [Configure an account programmatically](/developers/sdk-setup/configure-programmatically.md), and [Ways to configure an account](/guides/ways-to-configure.md) for the five routes.
* Designing the role model itself: [Design roles and permissions](/guides/roles-and-permissions.md).
* Pinning versions: [Releases and compatibility](/resources/releases.md) for the pinned Protocol release and which package versions match these pages.
* Checking a ceiling before you build against it: [Limits and defaults](/resources/limits-and-defaults.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bloxchain.app/developers/developers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.