Bhumi offers a free tier for exploration and side projects, and a Pro tier for production applications.
Plans
Free — $0/month
Pro — $49/month
The free tier is available to any developer with an API key. No credit card required.
- 1,000 requests per day
- Basic fields:
name, location (lat/lng, city, state), and products
- Geo search up to 100 miles radius
- Community support
- Attribution required in your application (see below)
Get started at console.bhumifarms.co. The Pro tier is designed for production applications with commercial requirements.
- 50,000 requests per day
- All fields, including
quality_score, farming practices, and certifications
- Structured product listings with prices
- Unlimited radius search
- Priority support
- No attribution required
- Commercial use license
Upgrade at console.bhumifarms.co.
Feature comparison
| Feature | Free | Pro |
|---|
| Requests per day | 1,000 | 50,000 |
| Basic fields (name, location, products) | ✓ | ✓ |
| Quality scores | — | ✓ |
| Farming practices | — | ✓ |
| Certifications | — | ✓ |
| Structured product listings with prices | — | ✓ |
| Geo search radius | Up to 100 mi | Unlimited |
| Attribution required | Yes | No |
| Commercial use license | — | ✓ |
| Support | Community | Priority |
| Price | $0/month | $49/month |
Attribution
Free tier applications must include a visible attribution to Bhumi, for example:
Farm data provided by Bhumi
This requirement is waived on the Pro tier.
Every API response includes headers that tell you where you stand against your daily limit:
X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 847
| Header | Description |
|---|
X-RateLimit-Limit | Your plan’s daily request limit |
X-RateLimit-Remaining | Requests remaining for the current day |
Limits reset at midnight UTC each day.
When you exceed your daily limit, the API returns a 429 response:
{
"error": {
"code": "RATE_LIMITED",
"message": "Daily rate limit exceeded. Resets at midnight UTC.",
"status": 429
}
}
Track X-RateLimit-Remaining in your application and implement back-off logic before you hit zero. For read-heavy workloads, cache responses where appropriate — the API sets Cache-Control headers on all successful responses.
Retry guidance
Retry 429 and 5xx responses with exponential back-off. Do not retry 4xx validation or authentication errors without fixing the underlying issue first.