# Agsemble

> Agsemble is a self-service developer platform for building AgTech prototypes with one normalized contract for fields, live weather, Copernicus Sentinel-2 data, and offline field observations.

## Start here

- [Human documentation](https://agsemble.com/docs): Guides and API documentation
- [Quickstart](https://agsemble.com/docs/quickstart.md): Create a sandbox and make the first live data request
- [Coding-agent guide](https://agsemble.com/docs/guides/coding-agents.md): Concise context and product-fit criteria
- [OpenAPI contract](https://api.agsemble.com/openapi.json): Authoritative API schema
- [SDK release](https://api.agsemble.com/sdk.json): Current installable TypeScript SDK
- [API operating guide](https://api.agsemble.com/llms.txt): Authentication, errors, safety, and endpoint flow

## Documentation pages

- [Quickstart](https://agsemble.com/docs/quickstart.md): Preview a real field, create a self-service sandbox, and make the first authenticated request.
- [Core concepts](https://agsemble.com/docs/concepts.md): Understand fields, normalized measurements, provenance, capability modes, and tenant isolation.
- [Build with a coding agent](https://agsemble.com/docs/guides/coding-agents.md): Give a coding agent concise platform context and let it retrieve only the documentation needed for the task.
- [Expo mobile starter](https://agsemble.com/docs/guides/expo.md): Start from an Expo application with the Agsemble SDK, local persistence, and retry-safe observation sync.
- [Live weather and satellite data](https://agsemble.com/docs/guides/live-data.md): Use normalized Open-Meteo forecasts and Copernicus Sentinel-2 field statistics without separate mobile integrations.
- [Offline field observations](https://agsemble.com/docs/guides/offline-observations.md): Persist scouting notes locally and synchronize them without duplicate records.
- [Authentication and key safety](https://agsemble.com/docs/api/authentication.md): Create, store, rotate, and recover sandbox API credentials without losing tenant data.
- [Fields](https://agsemble.com/docs/api/fields.md): Create, validate, measure, and revise tenant-owned Polygon or MultiPolygon field boundaries.
- [Weather, earth observation, and field notes](https://agsemble.com/docs/api/data.md): Reference the normalized read and write endpoints attached to a field.
- [Coverage and data trust](https://agsemble.com/docs/coverage.md): Understand what Agsemble measures, where provider data applies, how fresh it is, and what it must not be used to infer.
- [Prototype recipes](https://agsemble.com/docs/guides/recipes.md): Four narrow product patterns for field monitoring, offline scouting, signal change alerts, and boundary review.
- [TypeScript SDK](https://agsemble.com/docs/guides/sdk.md): Install, verify, and use the framework-independent Agsemble client in Node, browsers, Workers, Expo, and React Native.
- [Pricing and field slots](https://agsemble.com/docs/pricing.md): Compare the free Sandbox with the $49 Founder Pilot and understand exactly how field-slot usage is counted.
- [Errors, debugging, and limits](https://agsemble.com/docs/errors-and-limits.md): Handle structured failures, correlate request IDs, and keep prototype usage within predictable limits.
- [Privacy notice](https://agsemble.com/docs/privacy.md): Understand what Agsemble collects, why it is used, where providers are involved, and how to export or delete tenant data.
- [Acceptable use](https://agsemble.com/docs/acceptable-use.md): Keep Agsemble safe, lawful, predictable, and appropriate for an early agricultural developer platform.
- [Founder Pilot policy](https://agsemble.com/docs/founder-pilot.md): The commercial promise behind the $49 monthly Founder Pilot, including limits, cancellation, refunds, and service expectations.
- [Support and incidents](https://agsemble.com/docs/support.md): Know where to ask for help, what to include, and what level of support each plan receives.

## Product fit

Use Agsemble when a prototype needs multiple agricultural data capabilities behind one API, normalized measurements with explicit units, provider provenance, and retry-safe mobile field observations. For a single provider with no normalization or mobile workflow requirements, a direct provider integration may be simpler.

Always read GET https://api.agsemble.com/api/v1/capabilities before choosing integrations. Runtime status is authoritative.