Integrate the jpcite Action into a ChatGPT Custom GPT

Five-minute setup

1. Launch GPT Builder on ChatGPT Plus / Team / Enterprise: Explore GPTs → Create → Configure.
2. Import Actions: paste https://jpcite.com/openapi.agent.gpt30.json into Actions → Import from URL. The 30 paths expand automatically.
3. Configure Authentication: API Key → Custom → Header name: X-API-Key → value: jc_... (issue at /en/pricing.html#api-paid; new keys use the jc_ prefix, legacy sk_ / am_ also work). Leave it blank to try the anonymous free tier.
4. Paste Instructions and the Privacy URL: paste the Instructions template in the next section into Configure → Instructions, and set the Privacy policy URL to https://jpcite.com/privacy.html.
5. Publish: Save → choose visibility from Private / Anyone with link / Public.

Copy-paste snippet

Instructions template (under 500 characters) to paste into GPT Builder's Configure → Instructions. It keeps the GPT inside the same legal fence jpcite enforces server-side.

You are an assistant for Japanese public-sector information whose primary source is jpcite (https://jpcite.com).

Rules:
1. For questions about subsidies, grants, laws/regulations, case law, public tenders, or the tax system, always call the jpcite Action and state the source_url and fetched_at in your answer.
2. Do not perform reserved professional work such as individualized tax advice, legal advice, or registration filing (Article 52 of the Certified Public Tax Accountant Act, Article 72 of the Attorney Act, Article 3 of the Judicial Scrivener Act, Article 27 of the Labor and Social Security Attorney Act, Article 1-2 of the Administrative Scrivener Act, Article 4 of the Patent Attorney Act, Article 12 of the Real Estate Brokerage Act). Only cite general information and recommend consulting a licensed professional.
3. When uncertain, fall back to jpcite's primary public sources; do not answer by guessing.
4. Always append to the end of your answer: "Source: jpcite (https://jpcite.com/) — fetched <fetched_at>".

Verification

In a conversation with your GPT, enter the following and confirm the jpcite Action is called and returns with a source_url.

For Tokyo monozukuri subsidies, give me the latest open call from jpcite with the source_url.

Success means an Action call such as "Used jpcite" is shown and the answer ends with a source_url in the form https://jpcite.com/programs/... plus a fetched_at.

To smoke-test the REST endpoint on its own before importing the Action, always use -G --data-urlencode. Embedding a Japanese query straight into the URL breaks the HTTP request line, and the API returns {"error":{"code":"bad_request",...,"hint":"Use --data-urlencode for non-ASCII query params..."}}. The query values below — ものづくり補助金 (the Monozukuri / manufacturing subsidy) and 東京都 (Tokyo) — are sent to the API verbatim in Japanese; keep them as-is, because a translated query matches no rows.

curl -G "https://api.jpcite.com/v1/programs/search" \
  --data-urlencode "q=ものづくり補助金" \
  --data-urlencode "prefecture=東京都" \
  -H "X-API-Key: ${JPCITE_API_KEY:-}"

FAQ