Developer Starter Repos

Purpose

Give external developers a fast, safe path to build on Norynta without needing private repo context or live trading permissions on day one.

Recommended first starters

Use examples/starter-bot/ when a developer wants a copyable external repo with watch, plan, and opt-in trade modes:

cd examples/starter-bot
npm install
cp .env.example .env
npm run watch

Use starters/liquidity-bot/ when a developer wants the smallest dry-run first-liquidity quote planner:

cd starters/liquidity-bot
npm install
cp .env.example .env
npm run dry-run

From the root repo you can also run:

npm run bot:starter:dry-run

Both starters discover markets, read public/API surfaces, and keep live writes off by default. The liquidity starter intentionally stops before live writes even if NORYNTA_EXECUTE=1 is set.

Copyable SDK Template

For a standalone repository skeleton, copy:

cp -R examples/starter-bot ../norynta-starter-bot
cd ../norynta-starter-bot
npm install
cp .env.example .env
npm run watch

This template uses the published @norynta/bot-sdk, so it is closer to what an external developer would run outside the private monorepo. It supports watch, plan, and explicitly gated limit-order write mode.

Auto-Trader Example

The root repo also includes:

npm run bot:auto-trader

It is dry-run by default and proposes small quote candidates from snapshots. Only enable live writes after adding wallet funding limits, jurisdiction checks, stale quote cancellation, idempotency, and monitoring.

What developers can build first

• market watcher and alert bot
• request-backed market discovery bot
• first-liquidity quote planner
• data dashboard using public market and event snapshots
• reconciliation monitor using snapshots plus streams
• maker workflow that graduates from dry-run to approved live access

Graduation path

1. Run the starter against local or devnet.
2. Add explicit risk limits, cancellation, idempotency, and alerting.
3. Complete npm run agent:conformance.
4. Request API or maker access.
5. Start with dry-run or limited sandbox sessions.
6. Move to production only after review and jurisdiction checks.

Safety defaults

Starters should default to:

• no live writes
• no private keys in source
• explicit notional caps
• quote TTLs and stale quote cancellation
• one market/category at a time
• idempotency keys on every write
• logs that are useful for support without exposing secrets

Related docs

• docs/public/DEVELOPER_QUICKSTART.md
• docs/public/SDK_AND_EXAMPLES.md
• docs/public/AGENT_BOT_READINESS_CHECKLIST.md
• docs/public/TRADING_INTEGRATION_WORKFLOW.md
• docs/public/LIQUIDITY_PARTNERS.md