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

# Developers

For programmatic traders and developers, please ask us for access to our Github repo. We will soon publish the whole front-end code and all SDKs. Until we are able, please ask us for private access.

See [Developers](/developers/smart-contract-docs.md) for SDKs.

## Pretty Quick Start

Please read [/pages/ngDRVJDYHKtkLs6KAr0U#trade-only-access-i.e.-owner-trader-separation](https://docs.world.inc/getting-started/pages/ngDRVJDYHKtkLs6KAr0U#trade-only-access-i.e.-owner-trader-separation "mention") before you start writing production code, otherwise your nonce management will be hell. Most production setups use a multi-sig (i.e. Safe contract) or offline key as account Owner and designate 2 or more keys as trade-only keys. Currently, trading via trade-only keys is only available programmatically. In the near future, the UI will be updated to handle this perspective as well; you can set your keys with this delegated access in the UI. [This code](https://github.com/World-Markets-Inc/contract-owner) will be audited in the near future to securely automate depositing and withdrawing as well.

To save on gas costs and improve uptime, batch your orders into a single transaction. It is most common to batch a cancel and new order together to "reprice" limit orders. You can batch orders across markets and even across other venues on MegaETH. Order batching is not necessary for testing; it is important to be aware of before starting on your production code.

## MegaETH Mini-Blocks

Mini-blocks allow MegaETH to operate at 10ms block times. You need to use them for high frequency trading. Read [Mini-block docs](https://docs.megaeth.com/mini-block).

## Swap & Router Integration

swap\_router = 0x94b6706fa26a4f3dcf501ff25e1e4628b75adc69


---

# 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.world.inc/getting-started/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.