# Bazi calculator API selection checklist

Use this before adopting a provider or local package. Record the date and link for every answer.

- **Boundary:** Is this hosted HTTPS, local stdio/MCP, a local library, or an owned application source pack?
- **Input contract:** List required date, time, gender, language, timezone, and calendar fields. Do not infer omitted fields.
- **Time rules:** Does the documentation describe timezone, true solar time, daylight saving, or Korean calendar handling? Mark unknown when absent.
- **Output contract:** Record the named output fields and whether interpretation text is included. A field list is not an accuracy claim.
- **Access:** Is an API key needed? Where is it sent? Does a free tier use samples or permit arbitrary birth data?
- **Cost boundary:** Separate documented paid features from unknown production costs. Do not estimate usage pricing.
- **Runtime:** Note Node/Python/CLI requirements, local process behavior, deployment target, and data path.
- **Rights:** Record the license or commercial terms from the primary source. Confirm whether your intended project fits.
- **Data and notices:** Identify where personal birth data would travel and what privacy, legal, and third-party notices still need review.
- **Evidence date:** `checked_at`, locale, URL, and reviewer. Keep documentation evidence separate from runtime verification.
- **Decision:** Choose one boundary and write the first reversible test. Record unresolved questions before production.