Skip to content

Add shirabe.dev — Shirabe Calendar API 1.0.0 + Shirabe Address API 1.0.0#2452

Open
Shirabe-dev-sys wants to merge 1 commit into
APIs-guru:mainfrom
Shirabe-dev-sys:add-shirabe-dev-calendar-and-address-apis
Open

Add shirabe.dev — Shirabe Calendar API 1.0.0 + Shirabe Address API 1.0.0#2452
Shirabe-dev-sys wants to merge 1 commit into
APIs-guru:mainfrom
Shirabe-dev-sys:add-shirabe-dev-calendar-and-address-apis

Conversation

@Shirabe-dev-sys
Copy link
Copy Markdown

Adding Shirabe — a Japan-specific AI-native API platform by Techwell Inc.
Two OpenAPI 3.1.0 specs are included under the reverse-DNS path APIs/shirabe.dev/.

1. Shirabe Calendar API — APIs/shirabe.dev/calendar/1.0.0/openapi.yaml

Japanese calendar data (rokuyo 六曜, rekichu 暦注 / auspicious days, eto 干支, 24 solar terms) with purpose-specific auspicious-day scoring across 8 categories (wedding, funeral, moving, construction, business opening, car delivery, marriage registration, travel). Astronomical-precision lunar calendar engine.

2. Shirabe Address API — APIs/shirabe.dev/address/1.0.0/openapi.yaml

Japanese address normalization using the Address Base Registry (アドレス・ベース・レジストリ) published by Digital Agency of Japan under CC BY 4.0. Covers all 47 prefectures. Returns normalized string, structured components (prefecture / city / town / block / building / floor), postal code, WGS84 coordinates, match level, confidence score, and ABR attribution.

Validation

Both specs are:

  • OpenAPI 3.1.0 (validated with Redocly CLI and Swagger Editor)
  • Bilingual (Japanese + English) descriptions on every operation and schema
  • Available at stable canonical URLs (CORS open, no auth required for spec retrieval)
  • Designed for AI-agent consumption — compatible with ChatGPT GPTs Actions, Claude Tool Use, Gemini Function Calling, LangChain, Dify, and Model Context Protocol (Calendar API only for MCP at this time)

Operator / Contact

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant