Engawa Homes

Discover and buy real estate across Japan (akiya, kominka, mansions, land, and new-builds) with listing-source information, transit context, and yield estimates. Optional concierge support connects you to licensed local agents.

Engawa Homes is profiled on the APIs.io network. Tagged areas include Real Estate, Japan, Property, and Listings.

Engawa Homes’ developer surface includes engineering blog, pricing, and 12 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

12.1/100 emerging Agent 3/100 human only Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessOpen

0 APIs

Real Estate Japan Property Listings

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 12.1/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 0.4 / 17

Access Clarity 6.5 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 3.0 / 9

Regulatory Posture 2.6 / 15

Agent readiness — 3/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 7 / 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/engawahomes-com/"><img src="https://apis.io/badge/engawahomes-com/card.svg" alt="Engawa Homes 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 Ask about this →
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
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) Ask about this →
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) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →

12 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 Ask about this →
Developer Ergonomics scores 2.4 — up to +19.5 composite points Ask about this →
Operational Transparency scores 0.0 — up to +13.0 composite points Ask about this →

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.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

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/engawahomes-com/apis.yml: open an issue on github.com/api-evangelist/engawahomes-com 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 →

Engawa Homes API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Engawa Homes Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Engawa Homes Rate Limits

0 limits

RATE LIMITS

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

Engawa Homes

7 quoted statements, read from Engawa Homes's own page on 2026-11-09.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Engawa Homes

20 quoted statements, read from Engawa Homes's own page on 2026-11-09.

PRIVACY

Eligibility 1

Who may sign up and where, quoted from its own terms.

Engawa Homes

2 quoted statements, read from Engawa Homes's own page on 2026-11-09.

ELIGIBILITY

AI Preferences 1

Its stance on AI training, inference and agents, quoted from its own pages.

Engawa Homes

1 quoted statement, read from Engawa Homes's own page on 2026-11-09.

AI PREFS

Security Posture 2

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

Engawa Homes Authentication

0 schemes

SECURITY

Engawa Homes Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Engawa Homes Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Documentation 1

Reference material describing how the API behaves

AIPreferences

AIPreferences

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

UsageTerms

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 4

Properties that don't map to a standard resource type

Hosts

Vendors

DataProcessing

Eligibility

Source (apis.yml)

aid: engawahomes-com
name: Engawa Homes
description: Discover and buy real estate across Japan (akiya, kominka, mansions, land, and new-builds) with listing-source
  information, transit context, and yield estimates. Optional concierge support connects you to licensed local agents.
url: https://artifacts.apis.io/engawahomes-com/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-06 (modular-v1; was harvest)
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  label: Open access
  confidence: low
  probe_state: none
  source:
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
specificationVersion: '0.20'
created: '2026-11-06'
modified: '2026-11-06'
tags:
- Real Estate
- Japan
- Property
- Listings
tags_raw:
- real-estate
- japan
- property
- listings
- api
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: LLMsTxt
  url: llms/engawahomes-com-llms.txt
- type: WellKnown
  url: well-known/engawahomes-com-well-known.yml
- type: Hosts
  url: hosts/engawahomes-com-hosts.yml
- type: Vendors
  url: vendors/engawahomes-com-vendors.yml
- type: DomainSecurity
  url: security/engawahomes-com-domain-security.yml
- type: Website
  url: https://engawahomes.com/
- type: Blog
  url: https://engawahomes.com/blog
- type: Pricing
  url: https://engawahomes.com/pricing
- type: TermsOfService
  url: https://engawahomes.com/terms
- type: PrivacyPolicy
  url: https://engawahomes.com/privacy
- type: UsageTerms
  url: terms/engawahomes-com-terms-of-service.yml
- type: DataProcessing
  url: privacy/engawahomes-com-privacy-policy.yml
- type: Eligibility
  url: eligibility/engawahomes-com-eligibility.yml
- type: AIPreferences
  url: ai-preferences/engawahomes-com-ai-preferences.yml
apis: []
x-coverage:
  state: none
  reason: no-developer-program
  detail: No public API documentation or machine-readable contract found after probing common spec URLs.
  evidence:
  - url: https://engawahomes.com/openapi.json
    status: 404
  checked: '2026-11-07'
x-enrichment:
  date: '2026-11-06'
  status: enriched
  artifacts_added: 24
  pass: modular-v1
  engine: identity=oss,contract=oss,surfaces=oss,docs=oss,regulatory=oss

Engawa Homes API — frequently asked questions

How do I authenticate with the Engawa Homes API?

Engawa Homes documents its authentication (0 schemes). The details are profiled on APIs.io as Engawa Homes Authentication.

Is the Engawa Homes API ready for AI agents?

Engawa Homes has a Kin Score of 12.1 out of 100 (emerging) and an Agent Readiness score of 2.5 (human-only), scored by API Evangelist on 2026-11-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/engawahomes-com"

All providers

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

Every operation they expose

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

How their score was established

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