Oishii

Oishii is a US vertical-farming company founded in 2016 and headquartered in Jersey City, New Jersey, that grows pesticide-free Japanese strawberry varieties — the Omakase Berry and Koyo Berry — plus the Rubi Tomato inside robot-assisted, bee-pollinated indoor "Smart Farms" in New Jersey, and sells them direct-to-consumer and through grocery retail across the United States and Canada. Oishii publishes no traditional developer program, but its direct-to-consumer storefront at oishii.com runs on Shopify and therefore exposes a real, anonymous, machine-readable agent-commerce surface: an /agents.md and /llms.txt agent instruction document, a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp, OAuth 2.0 and OpenID Connect discovery documents, a live storefront MCP server at /api/mcp exposing catalog search, cart, product-detail and policy-lookup tools, and a UCP checkout MCP endpoint at /api/ucp/mcp that is gated behind an agent profile URI.

Oishii is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Agriculture, Vertical Farming, Food and Beverage, and Consumer Products.

Oishii’s developer surface includes documentation, support, engineering blog, signup flow, authentication, and 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

26.5/100 thin ▬ flat Agent 24/100 agent aware Front door AI 1/6 silent Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 APIs 1 MCP Servers 1 Agent Skills

Company Agriculture Vertical Farming Food and Beverage Consumer Products E-Commerce Retail Agentic Commerce Shopify MCP Universal Commerce Protocol

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 26.5/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 6.1 / 17

Access Clarity 5.8 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 6.4 / 9

Regulatory Posture 5.1 / 15

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 5 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

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.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/oishii/"><img src="https://apis.io/badge/oishii/card.svg" alt="Oishii on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 34.2 — up to +13.2 composite points
Operational Transparency scores 0.0 — up to +13.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/oishii/apis.yml: open an issue on github.com/api-evangelist/oishii to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 4

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

Universal Commerce Protocol (UCP)

measured — observed by APIs.io (shopify)

Agent Skills

measured — observed by APIs.io (published)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Oishii Storefront MCP Server

Anonymous, live Model Context Protocol server for the Oishii storefront, served from oishii.com and provided by the Shopify storefront-renderer platform. A tools/list call retur...

Oishii UCP Agentic Commerce Endpoint

Universal Commerce Protocol (UCP) endpoint for agent-driven purchasing from the Oishii store, advertised in the merchant profile at https://oishii.com/.well-known/ucp with suppo...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Oishii MCP Server

Remote MCP server at oishii.com; 5 tools listed.

MCP SERVER

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

Shop the Oishii storefront via MCP

AGENT SKILL

Security Posture 2

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

Oishii Authentication

none/oauth2/openIdConnect · 4 schemes

SECURITY

Oishii Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Oishii Scopes

4 scopes · authorizationCode/refreshToken/urn:ietf:params:oauth:grant-type:jwt-bearer

4 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

WellKnown

MCPServer

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

Conventions

ErrorCatalog

Lifecycle

DataModel

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

Support

Support

HelpCenter

HelpCenter

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

SecondaryMarket

SecondaryMarket

Source (apis.yml)

aid: oishii
name: Oishii
description: 'Oishii is a US vertical-farming company founded in 2016 and headquartered in Jersey City, New Jersey, that grows
  pesticide-free Japanese strawberry varieties — the Omakase Berry and Koyo Berry — plus the Rubi Tomato inside robot-assisted,
  bee-pollinated indoor "Smart Farms" in New Jersey, and sells them direct-to-consumer and through grocery retail across the
  United States and Canada. Oishii publishes no traditional developer program, but its direct-to-consumer storefront at oishii.com
  runs on Shopify and therefore exposes a real, anonymous, machine-readable agent-commerce surface: an /agents.md and /llms.txt
  agent instruction document, a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp, OAuth 2.0 and OpenID
  Connect discovery documents, a live storefront MCP server at /api/mcp exposing catalog search, cart, product-detail and
  policy-lookup tools, and a UCP checkout MCP endpoint at /api/ucp/mcp that is gated behind an agent profile URI.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://oishii.com/cdn/shop/files/OishiiOGImage_24043e78-29c0-4975-8026-ea0399740ae4.jpg?v=1655908654
url: https://raw.githubusercontent.com/api-evangelist/oishii/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-platform: Shopify
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Agriculture
- Vertical Farming
- Food and Beverage
- Consumer Products
- E-Commerce
- Retail
- Agentic Commerce
- Shopify
- MCP
- Universal Commerce Protocol
tags_raw:
- Company
- Agriculture
- Vertical Farming
- Food and Beverage
- Consumer Products
- Ecommerce
- Retail
- Agent Commerce
- Shopify
- MCP
- Universal Commerce Protocol
apis:
- name: Oishii Storefront MCP Server
  description: 'Anonymous, live Model Context Protocol server for the Oishii storefront, served from oishii.com and provided
    by the Shopify storefront-renderer platform. A tools/list call returns five tools with full JSON Schema input contracts:
    search_catalog (natural-language and filtered product search with cursor pagination), get_product_details, get_cart, update_cart,
    and search_shop_policies_and_faqs. Responses conform to the UCP catalog capabilities (dev.ucp.shopping.catalog.search
    / dev.ucp.shopping.catalog.lookup). No authentication is required for tools/list.'
  humanURL: https://oishii.com/agents.md
  baseURL: https://oishii.com/api/mcp
  tags:
  - MCP
  - Agentic Commerce
  - E-Commerce
  - Catalog
  - Shopify
  tags_raw:
  - MCP
  - Agent Commerce
  - Ecommerce
  - Catalog
  - Shopify
  properties:
  - type: MCPServer
    url: mcp/oishii-mcp.yml
  - type: Documentation
    url: https://oishii.com/agents.md
  - type: LLMsTxt
    url: llms/oishii-llms.txt
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: storefront-mcp
- name: Oishii UCP Agentic Commerce Endpoint
  description: 'Universal Commerce Protocol (UCP) endpoint for agent-driven purchasing from the Oishii store, advertised in
    the merchant profile at https://oishii.com/.well-known/ucp with supported protocol versions 2026-04-08 and 2026-01-23.
    It declares the cart, checkout, fulfillment, discount, order and catalog capabilities, plus Google Pay and Shopify card
    payment handlers. The MCP transport at /api/ucp/mcp is gated: an unauthenticated tools/list returns HTTP 422 with JSON-RPC
    error -32001 invalid_profile_url, because UCP requires the calling agent to present a profile URI. Checkout completion
    requires contemporaneous human buyer approval.'
  humanURL: https://oishii.com/.well-known/ucp
  baseURL: https://oishii.com/api/ucp/mcp
  tags:
  - Universal Commerce Protocol
  - Agentic Commerce
  - Checkout
  - Payments
  - MCP
  tags_raw:
  - Universal Commerce Protocol
  - Agent Commerce
  - Checkout
  - Payments
  - MCP
  properties:
  - type: Documentation
    url: https://oishii.com/agents.md
  - type: WellKnown
    url: well-known/oishii-well-known.yml
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: ucp
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/oishii-domain-security.yml
- type: Website
  url: https://oishii.com/
- type: SecondaryMarket
  url: https://forgeglobal.com/oishii_stock/
- type: Documentation
  url: https://oishii.com/agents.md
- type: Support
  url: https://oishii.com/pages/contact
- type: HelpCenter
  url: https://oishii.com/pages/faq
- type: Blog
  url: https://oishii.com/blogs/news
- type: SignUp
  url: https://oishii.com/account/login
- type: TermsOfService
  url: https://oishii.com/policies/terms-of-service
- type: PrivacyPolicy
  url: https://oishii.com/policies/privacy-policy
- type: LLMsTxt
  url: llms/oishii-llms.txt
- type: WellKnown
  url: well-known/oishii-well-known.yml
- type: MCPServer
  url: mcp/oishii-mcp.yml
- type: Authentication
  url: authentication/oishii-authentication.yml
- type: OAuthScopes
  url: scopes/oishii-scopes.yml
- type: Conformance
  url: conformance/oishii-conformance.yml
- type: Conventions
  url: conventions/oishii-conventions.yml
- type: ErrorCatalog
  url: errors/oishii-problem-types.yml
- type: Lifecycle
  url: lifecycle/oishii-lifecycle.yml
- type: DataModel
  url: data-model/oishii-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 19
  pass: local-v1

Oishii API — frequently asked questions

Does Oishii have an API?

Yes. APIs.io lists 2 APIs from Oishii, including Oishii Storefront MCP Server and Oishii UCP Agentic Commerce Endpoint.

How do I authenticate with the Oishii API?

Oishii documents its authentication (none/oauth2/openIdConnect · 4 schemes). The details are profiled on APIs.io as Oishii Authentication.

Does Oishii have an MCP server?

Yes. APIs.io lists 1 MCP server for Oishii: Remote MCP server at oishii.com; 5 tools listed.

Is the Oishii API ready for AI agents?

Oishii has a Kin Score of 26.5 out of 100 (thin) and an Agent Readiness score of 23.9 (agent-aware), scored by API Evangelist on 2026-11-06.

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/oishii"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/oishii/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/oishii/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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