Integrate the jpcite Action into a ChatGPT Custom GPT
Action import URL = https://jpcite.com/openapi.agent.gpt30.json. It is a profile carved from the 306-path public REST surface down to 34 agent-safe paths, then to 30 paths to fit the Custom GPT Actions limit.
Five-minute setup
- Launch GPT Builder on ChatGPT Plus / Team / Enterprise:
Explore GPTs → Create → Configure. - Import Actions: paste
https://jpcite.com/openapi.agent.gpt30.jsonintoActions → Import from URL. The 30 paths expand automatically. - Configure Authentication:
API Key→Custom→ Header name:X-API-Key→ value:jc_...(issue at /en/pricing.html#api-paid; new keys use thejc_prefix, legacysk_/am_also work). Leave it blank to try the anonymous free tier. - 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. - Publish:
Save→ choose visibility fromPrivate / Anyone with link / Public.
Copy-paste snippet
Instructions template (under 500 characters) to paste into GPT Builder's Configure → Instructions. Keep the Japanese rule text verbatim so the GPT enforces the same legal fence.
あなたは jpcite (https://jpcite.com) を主な情報源とする日本公的情報アシスタントです。
ルール:
1. 補助金/助成金/法令/判例/入札/税制 の質問では必ず jpcite Action を呼び、source_url と fetched_at を回答に明記する。
2. 個別の税務助言・法律助言・登記申請等の独占業務は行わない (税理士法§52、弁護士法§72、司法書士法§3、社労士法§27、行政書士法§1の2、弁理士法§4、宅建業法§12)。一般情報の引用と「専門家への相談を推奨」のみ。
3. 不確実な場合は jpcite の公的一次情報に立ち戻り、推測で回答しない。
4. 回答末尾に "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..."}}.
curl -G "https://api.jpcite.com/v1/programs/search" \
--data-urlencode "q=ものづくり補助金" \
--data-urlencode "prefecture=東京都" \
-H "X-API-Key: ${JPCITE_API_KEY:-}"
FAQ
Why the 30-path limit?
The public REST surface has 306 paths, the agent-safe OpenAPI has 34 paths, and the ChatGPT profile is 30 paths to fit the Custom GPT Actions limit of 30 operations. The full set of 261 MCP tools is available over MCP (Claude Code / Cursor / Codex).
How do I issue an API key?
Issue one from /en/pricing.html#api-paid via Stripe Checkout (consent is in custom_text.submit.message). The dashboard shows your jc_... key right afterward (new keys use the jc_ prefix; legacy sk_ / am_ also work). You can try the anonymous free tier too, but it is capped at 3 req/IP/day.
What is the 8-profession legal fence?
jpcite does not return individualized advice that would intrude on the exclusive practice areas under the Certified Tax Accountant Act §52, the Attorney Act §72, and similar statutes. See /en/legal-fence.html. Writing this into Instructions keeps the GPT itself from stepping into those exclusive practice areas.