# Agri Info Design, Ltd. (株式会社農業情報設計社) > Japanese agricultural-technology company in Obihiro, Hokkaido, founded 21 April 2014. Builds the > AgriBus precision-farming line: the AgriBus-NAVI Android GPS/GNSS guidance app for tractors > (100,000+ downloads worldwide), AgriBus-GMiniR and AgriBus-G2 RTK-GNSS receivers, the > AgriBus-AutoSteer automatic steering package, and AgriBus-Web, a browser console for fields, > guidance lines, work history, elevation maps and RTK base stations. Also sells ISOBUS / ISO 11783 / > AG-PORT consulting. GENERATED BY API EVANGELIST. Agri Info Design does not publish an llms.txt. This file is assembled from the company's public website and from the four machine-readable API contracts its platform serves anonymously. It is not a provider publication and must not be cited as one. Generated 2026-09-12. Source of record: https://github.com/api-evangelist/agriinfodesign ## The short version for an agent Agri Info Design has a substantial, real, machine-readable API surface — 186 operations across four contracts — and **no developer program whatsoever**. There is no developer portal, no API reference, no getting-started guide, no authentication documentation, no SDK in any language, no CLI, no sandbox, no status page, no changelog, no rate limits, no error catalogue and no documented way for a third party to obtain a credential. The contracts are served publicly because springdoc and Springfox serve them by default, not because the company published them for you. ## Contracts (harvested verbatim, served anonymously by the provider) - [AgriBus Datastore API](https://datastore.agribus-connect.net/v3/api-docs): OpenAPI 3.0.1, 50 paths / 61 operations. Fields, reference lines, work records, plantings, soil-moisture and accumulated-temperature observations, elevation maps — plus the 農機オープンAPI (Agricultural Machinery Open API v2.0.0) device and location surface. - [AgriBus Authentication & OpenID Connect API](https://auth.agribus-connect.net/v3/api-docs): OpenAPI 3.0.1, 20 paths / 22 operations. Sign-up, sign-in, profile, groups, Firebase custom tokens, RTK caster settings, OAuth 2.0 / OIDC authorization, impersonation. - [AgriBus-Web Manager API](https://manager.agribus-connect.net/swagger-resources): Swagger 2.0, 71 paths. Devices, users, tokens, teams, web markers, search, system administration, RTK caster and Stripe billing, in v1 and v2 generations. - [AgriBus Billing & Payments API](https://pay.agribus-connect.net/v3/api-docs): OpenAPI 3.0.1, 21 paths / 22 operations. Stripe subscriptions, cards, coupons, invoices; Google Play purchase verification; AgriBus-DWH market-monitor tokens. ## Identity and authorization (live documents) - [OpenID Connect discovery](https://auth.agribus-connect.net/.well-known/openid_configuration) — note the **underscore**. The standard hyphenated path returns 404, so a conformant client cannot discover this issuer. The document also advertises a *development* issuer (manager-development.agribus-connect.net). - [JWKS](https://auth.agribus-connect.net/.well-known/jwks.json) — one RSA key, kid `connect-auth-key-1`, RS256. - [Agricultural machinery OAuth scope catalogue](https://auth.agribus-connect.net/v1/agricultural-api/oauth/scopes) — ten `noki.*` scopes covering devices, locations, work records, environmental data and field boundaries, read and write, plus `noki.admin`. Served without credentials. Only two of the ten have a published operation behind them. ## Domain standard The datastore contract declares 農機オープンAPI v2.0.0 in its own tag metadata and implements the device and location surface of the Japanese cross-vendor machine-data standard coordinated by NARO under MAFF's agricultural data-infrastructure programme — `GET /v1/agricultural-machinery/devices` and `GET /v1/agricultural-machinery/devices/{device_id}/locations`, the latter returning RFC 7946 GeoJSON. Since FY2022 MAFF has conditioned agricultural-machinery subsidies on manufacturers providing open-API data linkage, which is the context this surface exists in. ## Company and product pages - [Website](https://agri-info-design.com/) - [Company / about](https://agri-info-design.com/en/company/) - [Products](https://agri-info-design.com/en/product/) - [AgriBus-Web](https://agri-info-design.com/en/agribus-web/) - [AgriBus-NAVI](https://agri-info-design.com/en/agribus-navi/) - [ISOBUS consulting](https://agri-info-design.com/en/consulting/) - [Plan comparison](https://agri-info-design.com/en/plan-comparison-chart/) — Free, Plus (USD 134.99 / JPY 19,800 per year), Professional (USD 274.99 / JPY 39,800 per year), Enterprise on request. Free-tier work data is retained **2 days**. - [AgriBus-Web console](https://app.agribus-connect.com/) - [Online store](https://shop.agri-info-design.com/) - [Help centre](https://support.agri-info-design.com/) - [News / blog](https://agri-info-design.com/en/news/) ([RSS](https://agri-info-design.com/en/feed/)) - [Terms of use](https://agri-info-design.com/term/) · [Privacy policy](https://agri-info-design.com/privacy-policy/) · [特定商取引法に基づく表記](https://agri-info-design.com/transactions/) - [GitHub organisation](https://github.com/agri-info-design) - [AgriBus-NAVI on Google Play](https://play.google.com/store/apps/details?id=com.agri_info_design.AgriBusNavi) ## What an agent must know before calling anything - **Auth:** `Authorization: Bearer ` issued by auth.agribus-connect.net. An unauthenticated call returns **403**, not 401, with no `WWW-Authenticate` header — and **500** on the pay service, which is a defect. - **Errors:** no contract declares a single non-200 response across all 186 operations. Two vendor envelopes are used live: `{"code":"IAM-…","message":"…"}` and the Spring default `{"timestamp","status","error","path"}`. No RFC 9457. - **Idempotency:** none. No `Idempotency-Key` anywhere, including on the money-moving billing writes. - **Rate limits:** none published, and no `RateLimit-*`, `X-RateLimit-*` or `Retry-After` header is ever emitted. - **Reversibility:** delete is the only undo, there is no undo for an edit, and no retention or refund window is stated anywhere — including on the Japanese commercial-transactions disclosure page where a Japanese seller would normally state a refund policy. - **Deprecations:** 13 operations are flagged deprecated in the specs with no sunset date, no replacement pointer and no RFC 8594 headers on the live routes. - **MCP / A2A:** neither. No MCP server and no agent card exist. Do not look for one. ## API Evangelist artifacts in this repository - `openapi/` — the four contracts, verbatim, plus `_original/` - `overlays/` — OpenAPI Overlay 1.0.0 documents recording our enhancements (the specs ship `info: null` and `http://` servers) - `authentication/`, `scopes/` — auth profile and the live scope catalogue - `conventions/` — pagination, idempotency (`coverage: none`) and reversibility - `errors/` — the error envelopes, probed live because the contracts declare none - `data-model/` — the entity graph and the spec-hygiene findings - `lifecycle/` — the 13 deprecated operations; no status page, no changelog, no SLA - `conformance/` — OpenAPI, OAuth2, OIDC, GeoJSON, and the 農機オープンAPI domain-standard signature - `plans/`, `rate-limits/`, `packages/`, `well-known/`, `security/`, `mcp/`, `skills/`