Agripedia

Agripedia (アグリぺディア株式会社) is a Tokyo agricultural technology company, founded in June 2019 and headquartered in Nishi-Gotanda, Shinagawa-ku, that connects mid- and large-scale Japanese farms and production areas with food-service and food-manufacturing buyers. It supports growers from GAP certification through to the sale of the certified produce, runs a B2B direct-sales channel for GAP-certified commercial agricultural products, sells crop-protection materials and fertilizer, and operates its own production management system for cultivation history and traceability. It holds JGAP group certification (March 2023) and is a GAP partner of Japan's Ministry of Agriculture, Forestry and Fisheries. Its software reaches farms, buyers and staff as closed, credentialed web applications; the company publishes no developer program, no public API, and no machine-readable contract on any host it operates.

Agripedia is profiled on the APIs.io network. Tagged areas include Company, Agriculture, AgTech, Farm Management, and Food Supply Chain.

Agripedia’s developer surface includes engineering blog and 9 more developer resources.

8.3/100 minimal Agent 0/100 human only Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
0 APIs
CompanyAgricultureAgTechFarm ManagementFood Supply ChainTraceabilityGAP CertificationB2B MarketplaceJapan

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/agripedia: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Agripedia Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Commercial 1

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: agripedia
name: Agripedia
description: Agripedia (アグリぺディア株式会社) is a Tokyo agricultural technology company, founded in June 2019 and headquartered in
  Nishi-Gotanda, Shinagawa-ku, that connects mid- and large-scale Japanese farms and production areas with food-service and
  food-manufacturing buyers. It supports growers from GAP certification through to the sale of the certified produce, runs
  a B2B direct-sales channel for GAP-certified commercial agricultural products, sells crop-protection materials and fertilizer,
  and operates its own production management system for cultivation history and traceability. It holds JGAP group certification
  (March 2023) and is a GAP partner of Japan's Ministry of Agriculture, Forestry and Fisheries. Its software reaches farms,
  buyers and staff as closed, credentialed web applications; the company publishes no developer program, no public API, and
  no machine-readable contract on any host it operates.
url: https://raw.githubusercontent.com/api-evangelist/agripedia/refs/heads/main/apis.yml
image: https://storage.googleapis.com/production-os-assets/assets/b88741c2-9769-459d-8a72-ec63d33322a4
x-type: company
x-source: harvest:secondary-market
x-tier: stub
x-tier-reason: harvest
specificationVersion: '0.20'
created: '2026-09-13'
modified: '2026-09-13'
tags:
- Company
- Agriculture
- AgTech
- Farm Management
- Food Supply Chain
- Traceability
- GAP Certification
- B2B Marketplace
- Japan
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://agripedia.co.jp/
- type: Newsroom
  url: https://agripedia.co.jp/news
- type: PrivacyPolicy
  url: https://agripedia.co.jp/news/detail/privacy_policy
- type: Blog
  url: https://note.com/agripedia
- type: BlogRSS
  url: https://note.com/agripedia/rss
- type: GitHubOrganization
  url: https://github.com/AgriPedia
- type: Careers
  url: https://herp.careers/careers/companies/agripedia
- type: SecondaryMarket
  url: https://equityzen.com/company/agripedia/
- type: DomainSecurity
  url: security/agripedia-domain-security.yml
- type: LLMsTxt
  url: llms/agripedia-llms.txt
x-enrichment:
  date: '2026-09-13'
  status: minimal
  artifacts_added: 3
  pass: local-v3
x-coverage:
  state: none
  reason: no-developer-program
  detail: 'Agripedia ships software only as closed end-user applications: its corporate site is a two-route Nuxt SPA (sitemap
    lists exactly / and /news) with no developer, docs, portal or integration link anywhere, kanri.agripedia.co.jp (AP管理システム)
    answers every path with a 401 "please register or sign in" body or a 302 to /users/sign_in, and connect.agripedia.co.jp
    calls itself "AgriPedia 社内向けSCMシステム" — an internal supply-chain tool — in its own meta description, so there is no public
    API being marketed and nothing gated behind a sales form either.'
  evidence:
  - url: https://agripedia.co.jp/
    status: 200
  - url: https://agripedia.co.jp/sitemap-static.xml
    status: 200
  - url: https://agripedia.co.jp/.well-known/zz-control-9f3a
    status: 200
  - url: https://material-sales.agripedia.co.jp/openapi.json
    status: 404
  - url: https://material-sales.agripedia.co.jp/graphql
    status: 404
  - url: https://material-sales.agripedia.co.jp/llms.txt
    status: 404
  - url: https://material-sales.agripedia.co.jp/.well-known/agent-card.json
    status: 404
  - url: https://material-sales.agripedia.co.jp/.well-known/api-catalog
    status: 404
  - url: https://kanri.agripedia.co.jp/openapi.json
    status: 401
  - url: https://kanri.agripedia.co.jp/api-docs
    status: 302
  - url: https://connect.agripedia.co.jp/openapi.json
    status: 200
  - url: https://registry.npmjs.org/agripedia
    status: 404
  checked: '2026-09-13'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/agripedia"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/agripedia/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/agripedia/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.