Connect jpcite REST/OpenAPI to OpenAI Codex CLI / Agents SDK

Five-minute setup

1. Review the OpenAPI spec: use https://jpcite.com/openapi.agent.gpt30.json or the API reference.
2. Create a REST helper: call https://api.jpcite.com/v1/programs/search with params and optional X-API-Key.
3. Bind it to an Agent: register that helper through your agent framework's function-tool mechanism.
4. (Optional) Pass an API key: set JPCITE_API_KEY to upgrade to metered mode. Leave it unset for the anonymous free tier.
5. For MCP: use uvx autonomath-mcp over stdio instead of a hosted HTTP endpoint.

Copy-paste snippet

A minimal REST helper that you can register as a function tool in your agent framework.

import os
import requests

def search_programs(q: str, prefecture: str = "東京都") -> dict:
    headers = {}
    if os.environ.get("JPCITE_API_KEY"):
        headers["X-API-Key"] = os.environ["JPCITE_API_KEY"]
    response = requests.get(
        "https://api.jpcite.com/v1/programs/search",
        params={"q": q, "prefecture": prefecture},
        headers=headers,
        timeout=20,
    )
    response.raise_for_status()
    return response.json()

# Register this helper through your Agents SDK / agent framework function-tool mechanism.
print(search_programs("ものづくり補助金", "東京都"))

Verification

Search ものづくり補助金 東京都 through REST and confirm that the JSON response includes source URLs. MCP tools are available through the stdio package; generation of 36-Agreement labor documents is not offered publicly.

When smoke-testing the REST endpoint directly, 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