HiCustomer

HiCustomer (ハイカスタマー) was a Japanese Customer Success Management (CSM) SaaS built specifically for SaaS companies. Its platform aggregated customer data scattered across BI tools, CRMs, and chat tools to visualize product usage, communication history, revenue, and contract information in one place. Teams used configurable health-score rules to monitor account health across the customer lifecycle, and custom alerts to surface churn and upsell signals at the right moment, with time-series analysis to make customer-success outreach repeatable. The company also offered customer-success consulting, and later pivoted to a digital sales room product, "Arch by HiCustomer". On 2024-09-13 HiCustomer Inc. sold the Arch business to the Tokyo-listed adtech company Geniee, Inc. (TSE 6562), which absorbed it into GENIEE SFA/CRM and rebranded it Geniee DSR. As of this enrichment pass the hicustomer.jp domain no longer resolves to a live site (its authoritative AWS Route 53 zone is delegated but empty) and the product is discontinued; the last archived homepage (Oct 2024) is a STUDIO-built single-page "About the company" placeholder. No public developer API, documentation, SDK, or developer portal was ever published — the Wayback record for hicustomer.jp contains no /api, /docs, /developers, /pricing or /status path at any point in its history.

HiCustomer is profiled on the APIs.io network. Tagged areas include Company, Customer Success, Customer Success Management, Software-as-a-Service, and Health Score.

🌐 Visit website 📡 Profile data on GitHub

0.0/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

0 APIs

Company Customer SuccessCustomer Success ManagementSoftware-as-a-ServiceHealth ScoreChurn Prediction Customer Data Platform Analytics Japan B2B SaaS Digital Sales Room Defunct

Kin Score

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

Composite quality — 0.0/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 0.0 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 0.0 / 9

Regulatory Posture 0.0 / 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 Health 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/hicustomer/"><img src="https://apis.io/badge/hicustomer/card.svg" alt="HiCustomer 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 0.0 — up to +20.0 composite points
Access Clarity scores 0.0 — up to +20.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/hicustomer/apis.yml: open an issue on github.com/api-evangelist/hicustomer 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)	long-tail	2.5 (thin)	-	1

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.

Resources

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: hicustomer
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: none
  source: []
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/hicustomer.png
name: HiCustomer
description: HiCustomer (ハイカスタマー) was a Japanese Customer Success Management (CSM) SaaS built specifically for SaaS companies.
  Its platform aggregated customer data scattered across BI tools, CRMs, and chat tools to visualize product usage, communication
  history, revenue, and contract information in one place. Teams used configurable health-score rules to monitor account health
  across the customer lifecycle, and custom alerts to surface churn and upsell signals at the right moment, with time-series
  analysis to make customer-success outreach repeatable. The company also offered customer-success consulting, and later pivoted
  to a digital sales room product, "Arch by HiCustomer". On 2024-09-13 HiCustomer Inc. sold the Arch business to the Tokyo-listed
  adtech company Geniee, Inc. (TSE 6562), which absorbed it into GENIEE SFA/CRM and rebranded it Geniee DSR. As of this enrichment
  pass the hicustomer.jp domain no longer resolves to a live site (its authoritative AWS Route 53 zone is delegated but empty)
  and the product is discontinued; the last archived homepage (Oct 2024) is a STUDIO-built single-page "About the company"
  placeholder. No public developer API, documentation, SDK, or developer portal was ever published — the Wayback record for
  hicustomer.jp contains no /api, /docs, /developers, /pricing or /status path at any point in its history.
url: https://raw.githubusercontent.com/api-evangelist/hicustomer/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: stub
x-tier-reason: portfolio-lead
x-status: defunct
x-status-reason: 'hicustomer.jp has no A/CNAME/MX/TXT records in its authoritative AWS Route 53 zone (re-probed 2026-08-13:
  NS delegated to ns-481/ns-1008/ns-1515/ns-1943 awsdns, WHOIS ACTIVE, zone empty; every HTTPS request returns curl exit 6
  / status 000). Site is dark. The successor product "Arch by HiCustomer" was divested to Geniee, Inc. (TSE 6562) on 2024-09-13
  and rebranded Geniee DSR. No API surface, ever.'
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-09-16'
tags:
- Company
- Customer Success
- Customer Success Management
- Software-as-a-Service
- Health Score
- Churn Prediction
- Customer Data Platform
- Analytics
- Japan
- B2B SaaS
- Digital Sales Room
- Defunct
tags_raw:
- Company
- Customer Success
- Customer Success Management
- SaaS
- Health Score
- Churn Prediction
- Customer Data Platform
- Analytics
- Japan
- B2B SaaS
- Digital Sales Room
- Defunct
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://hicustomer.jp
x-enrichment:
  date: '2026-08-13'
  status: nochange
  artifacts_added: 0
  pass: local-v1
x-coverage:
  state: none
  reason: defunct
  detail: hicustomer.jp is a registered .jp domain delegated to AWS Route 53 with a completely empty zone — no A, CNAME or
    MX answer for the apex or for any api/docs/app subdomain — so every probe fails at DNS, and the company's last remaining
    product, the "Arch by HiCustomer" digital sales room, was sold to Geniee, Inc. on 2024-09-13 and now ships as Geniee DSR.
  evidence:
  - url: https://hicustomer.jp/
    status: 0
  - url: https://api.hicustomer.jp/
    status: 0
  - url: https://hicustomer.jp/openapi.json
    status: 0
  - url: https://hicustomer.jp/.well-known/agent-card.json
    status: 0
  - url: https://web.archive.org/web/20240523185505id_/https://hicustomer.jp/.well-known/openid-configuration
    status: 200
  - url: https://geniee.co.jp/news/20240913/
    status: 200
  checked: '2026-08-13'
x-lifecycle:
  state: shuttered
  reason: domain-does-not-resolve
  observed: '2026-09-27'
  detail: The company's own domain returned no A or AAAA record when probed. This is an observation about the domain, not
    a request from the company.
  indexed: false

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

All providers

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

Every operation they expose

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

How their score was established

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