Ulysses (Kaminashi)

Kaminashi Inc. (株式会社カミナシ) is a Tokyo-based SaaS company founded in December 2016 under its former corporate name Ulysses Inc. (ユリシーズ株式会社). It builds the Kaminashi frontline-operations DX platform for deskless workers — digital checklists and inspections, equipment maintenance (CMMS), frontline employee management, training and manuals, and reporting — serving food manufacturing, machine manufacturing, logistics, hotels, and building maintenance. Surfaced as a portfolio company of 500 Global and a16z. The company is ISMS (ISO/IEC 27001) certified and publishes no public developer API surface as of July 2026.

Ulysses (Kaminashi) is profiled on the APIs.io network. Tagged areas include Company, Software-as-a-Service, Frontline Operations, Manufacturing, and Food Safety.

Ulysses (Kaminashi)’s developer surface includes engineering blog, support, FAQ, product news, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

15.3/100 emerging ▬ flat Agent 0/100 human only Front door AI 1/6 silent Heartbeat 50/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

0 APIs

Company Software-as-a-Service Frontline Operations Manufacturing Food Safety CMMS TrainingDeskless WorkforceJapan

Kin Score

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

Composite quality — 15.3/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 1.2 / 17

Access Clarity 5.6 / 17

Operational Transparency 1.5 / 11

Contract Governance 0.0 / 10

Discoverability 4.8 / 9

Regulatory Posture 2.2 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 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 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 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/ulysses/"><img src="https://apis.io/badge/ulysses/card.svg" alt="Ulysses (Kaminashi) 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
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

13 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
Developer Ergonomics scores 7.1 — up to +18.6 composite points
Access Clarity scores 32.9 — up to +13.4 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/ulysses/apis.yml: open an issue on github.com/api-evangelist/ulysses 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Japan ISMAP Cloud Security Assessments (TISAX unreadable)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Security Posture 2

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

Ulysses Domain Security

TLSv1.3

SECURITY

Ulysses Trust Center

ISO 27001

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Security

TrustCenter

Compliance

Operate 3

Status, limits, changes, and where to get help

Support

Support

FAQ

FAQ

Contact

Contact

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 5

The organization behind the API

Website

Blog

EngineeringBlog

Careers

News

Other 2

Properties that don't map to a standard resource type

CorporateSite

CorporateSite

CaseStudies

CaseStudies

Source (apis.yml)

aid: ulysses
name: Ulysses (Kaminashi)
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 4
  pass: local-v1
description: Kaminashi Inc. (株式会社カミナシ) is a Tokyo-based SaaS company founded in December 2016 under its former corporate name
  Ulysses Inc. (ユリシーズ株式会社). It builds the Kaminashi frontline-operations DX platform for deskless workers — digital checklists
  and inspections, equipment maintenance (CMMS), frontline employee management, training and manuals, and reporting — serving
  food manufacturing, machine manufacturing, logistics, hotels, and building maintenance. Surfaced as a portfolio company
  of 500 Global and a16z. The company is ISMS (ISO/IEC 27001) certified and publishes no public developer API surface as of
  July 2026.
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:
  - security
  generated: '2026-11-06'
  method: derived
image: https://storage.googleapis.com/production-os-assets/assets/132450d6-2b17-4d66-9083-438c2b4df690
url: https://raw.githubusercontent.com/api-evangelist/ulysses/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
- a16z
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Software-as-a-Service
- Frontline Operations
- Manufacturing
- Food Safety
- CMMS
- Training
- Deskless Workforce
- Japan
tags_raw:
- Company
- SaaS
- Frontline Operations
- Manufacturing
- Food Safety
- CMMS
- Training
- Deskless Workforce
- Japan
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/ulysses-domain-security.yml
- type: Website
  url: https://kaminashi.jp
- type: CorporateSite
  url: https://corp.kaminashi.jp/
- type: Blog
  url: https://note.kaminashi.jp/
- type: EngineeringBlog
  url: https://kaminashi-developer.hatenablog.jp/
- type: Support
  url: https://kaminashi.jp/about/support
- type: FAQ
  url: https://kaminashi.jp/about/faq
- type: PrivacyPolicy
  url: https://corp.kaminashi.jp/privacy-policy
- type: Security
  url: https://corp.kaminashi.jp/security-policy
- type: TrustCenter
  url: security/ulysses-trust-center.yml
- type: Compliance
  url: https://kaminashi.jp/about/security
- type: Login
  url: https://kaminashi.jp/login
- type: GitHubOrganization
  url: https://github.com/kaminashi-inc
- type: Contact
  url: https://kaminashi.jp/contact/new
- type: CaseStudies
  url: https://kaminashi.jp/case/summary
- type: Careers
  url: https://careers.kaminashi.jp/
- type: News
  url: https://corp.kaminashi.jp/news
- type: LLMsTxt
  url: llms/ulysses-llms.txt

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

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/ulysses/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.