# AIHOJO External AI Client Guide

Generated at: 2026-06-13T23:31:34.662572+00:00
Base URL: https://aihojo.com/

This guide is for AI assistants, agent frameworks, MCP adapters, and operators that connect to AIHOJO public assets or APIs.

## Decision Boundary

- AIHOJO is informational only.
- Do not promise eligibility, approval, adoption, award probability, payment, or grant amount.
- Show official confirmation warnings and citations when presenting advice or report output.
- Treat AIHOJO output as a preparation memo for official pages, public guidelines, and expert review.

## Safe Discovery Order

1. Read `/llms.txt`.
2. Read `/ai-index.json` for scheme summaries, citations, freshness, public pages, and public resources.
3. Read `/openapi.json` before selecting any API operation.
4. For every OpenAPI operation, inspect `x-aihojo-action-class`.
5. For every OpenAPI operation, inspect `x-aihojo-requires-explicit-confirmation`.
6. Prefer `read` and `compute` operations before any operation that changes state or creates payment flow.
7. Require explicit user or operator confirmation before `user_write`, `payment`, `webhook`, or `ops_write`.

## Action Classes

| x-aihojo-action-class | Default handling |
| --- | --- |
| `read` | Safe to fetch for discovery or display. Still show official confirmation warnings when the content is used for decisions. |
| `compute` | Safe for provisional analysis. Do not treat the result as eligibility, approval, or award probability. |
| `user_write` | Ask for explicit user confirmation before calling. Explain what will be saved, shared, recorded, or changed. |
| `payment` | Ask for explicit user confirmation and show product, price, tier, and cancellation or refund context before calling. |
| `webhook` | Do not call manually unless an operator is testing a signed webhook path. A valid signature header is required. |
| `ops_write` | Operator-only. Require `OpsBearerAuth` and explicit operator confirmation. |

## Recommended Read-First Flow

1. `GET /v1/health`
2. `GET /v1/schemes`
3. `GET /v1/support/policy`
4. `GET /v1/status`
5. `POST /v1/advice` or `POST /v1/advice/conversation` when the user asks for guidance.
6. `POST /v1/reports/fit` when the user wants a structured fit report.

## Confirmation-Gated Flow

Only after the user has explicitly approved the specific action:

1. `POST /v1/reports/fit/save` to create a saved report receipt.
2. `POST /v1/reports/fit/saved/{id}/share` to enable or disable share-link access.
3. `POST /v1/checkout/sessions` to create a Stripe Checkout session.
4. `POST /v1/checkout/sessions/{id}/complete` to verify and complete checkout context.
5. `POST /v1/monitoring/watchlists` to create a monitoring watchlist.

## Runnable Connection Sample

- JavaScript sample: `/external-ai-client-example.mjs`
- URL: https://aihojo.com/external-ai-client-example.mjs
- The sample reads `/llms.txt`, `/ai-index.json`, and `/openapi.json` first.
- It allows `read` and `compute` operations, and refuses `user_write`, `payment`, `webhook`, and `ops_write` operations until the user or operator has explicitly confirmed the action.

## Safe Agent Pseudocode

```text
openapi = fetch_json("/openapi.json")
operation = openapi.paths[path][method]
action_class = operation["x-aihojo-action-class"]
requires_confirmation = operation["x-aihojo-requires-explicit-confirmation"]

if action_class in ["user_write", "payment", "webhook", "ops_write"] or requires_confirmation:
    stop and ask for explicit confirmation

call operation
show citations, freshness, and official confirmation boundary
```

## Input Safety

- Do not ask users to provide My Number, bank account numbers, passwords, API keys, private documents, or financial institution screening files.
- Prefer coarse business context: industry, location, planned cost category, rough budget, G-Biz ID status, quotation status, and self-funding readiness.
- If sensitive information appears in user input, tell the user not to submit it and continue with a redacted summary.

## Output Safety

- Say "official confirmation is required" when returning scheme advice.
- Cite official links and confirmation points.
- Distinguish "fit with stated needs" from "eligible", "approved", or "likely to be adopted".
- When information is missing, return the missing confirmation items rather than guessing.

## Current Scheme IDs

sch_digital_ai, sch_monodukuri_23, sch_regional_dx_it_adoption_tokyo, sch_shoryokuka_ippan