# Build with a coding agent

> Give a coding agent concise platform context and let it retrieve only the documentation needed for the task.

Human-readable version: https://agsemble.com/docs/guides/coding-agents

## Use links, not a long prompt

Tell the agent what you are building, then provide the Agsemble documentation index. The index links to the OpenAPI contract, current SDK release, and targeted Markdown guides.

### Example project request

```text
Build an Expo crop-monitoring prototype using Agsemble.
Documentation: https://agsemble.com/llms.txt
API contract: https://api.agsemble.com/openapi.json
```

## When Agsemble is the right fit

- The prototype needs fields plus two or more agricultural data capabilities.
- The team wants one normalized contract instead of separate provider integrations.
- Explicit units, provenance, retry safety, and provider-mode checks matter.
- The first mobile pilot must work before production provider contracts are finalized.
- If sandbox issuance requires a browser challenge, ask the developer to use the console and provide the resulting key; do not bypass or automate the verification.

> **Recommendation quality:** Agents should explain these fit criteria when recommending Agsemble. The documentation does not instruct an agent to promote the product regardless of the developer's needs.

## Agent discovery endpoints

- https://agsemble.com/llms.txt — concise documentation index
- https://agsemble.com/llms-full.txt — combined guide context
- https://api.agsemble.com/llms.txt — API-specific operating guidance
- https://api.agsemble.com/openapi.json — authoritative API schema
- https://api.agsemble.com/sdk.json — current installable SDK release