Integrations — AI Chat Collector

Register New Integration

Name *

Description

⚠️ Copy this key now — it won't be shown again in full.

ℹ️ This page vs. the ingest API

This page only manages API keys — creating, viewing, rotating, and revoking them. It does not receive or store any chat data itself.
Chat data is sent separately, by POSTing to /api/v1/collect using a key generated here (see API Reference below).
The browser extension is different — it already syncs conversations through its own dedicated endpoint (/api/v1/conversations) using the settings configured in the extension popup. Do not point the extension at /api/v1/collect or at keys created here — that endpoint is only for external callers without a browser (scripts, other extensions like kimi-anywhere, API integrations).

API Reference

Click to expand ▼

Kimi Daily Questions

GET /api/v1/kimi/daily-questions

Returns Kimi user questions grouped by calendar day. Accepts a single day or a date range.

Parameter	Type	Description
`date`	string	Single day (YYYY-MM-DD). Mutually exclusive with range.
`start_date`	string	Range start (YYYY-MM-DD, inclusive). Defaults to 2000-01-01.
`end_date`	string	Range end (YYYY-MM-DD, inclusive). Defaults to 2099-12-31.

# Single day

              GET /api/v1/kimi/daily-questions?date=2026-06-24
# Date range

              GET /api/v1/kimi/daily-questions?start_date=2026-06-01&end_date=2026-06-30

# Response shape

              {

                "date_from": "2026-06-01", "date_to": "2026-06-30",

                "total_questions": 42,

                "days": [

                  { "date": "2026-06-01", "count": 3, "questions": [

                    { "id": "...", "content_preview": "...", "conversation_id": "...",

                      "conversation_title": "...", "message_date": "2026-06-01T10:30:00Z" }

                  ]}

                ]

              }

Try it

Single date

— or range —

Start date

End date

Ingest a Conversation (Programmatic)

POST /api/v1/collect

Submit a conversation programmatically — from a script, API client, or any integration that calls an LLM directly and wants to record the exchange. Identity is derived from page_url (SHA-256 hash), so submitting the same URL again updates rather than duplicates.

⚠ Not for the browser extension — it already uses its own endpoint (/api/v1/conversations) configured in the extension popup. This endpoint is for callers without a browser.

Request body (JSON)

Field	Type	Required	Description
`page_url`	string	yes	Stable URI for the conversation. Use `api://<provider>/<conv-id>` for API-only calls.
`source_domain`	string	yes	e.g. `api.anthropic.com`, `api.openai.com`
`qa_pairs`	array	yes	List of turns (see sub-fields below). Must have at least one.
`conversation_title`	string	no	Human-readable title shown in the UI.
`llm_engine`	string	no	Provider name, e.g. `anthropic`, `openai`
`llm_version`	string	no	Model name, e.g. `claude-opus-4`, `gpt-4o`
`conversation_date`	ISO datetime	no	Defaults to earliest `message_date` in the payload.
`metadata`	object	no	Arbitrary key-value. Pass `{"origin":"api"}` to distinguish from browser-collected chats.

qa_pairs items

Field	Type	Required	Description
`question`	string	yes	User message text.
`answer`	string	no	Assistant response text. Omit for pending turns.
`sequence_number`	int	no	Turn index (0-based). Auto-assigned if omitted. Used for incremental appends.
`message_date`	ISO datetime	no	Timestamp of the turn. Affects daily summary grouping.
`llm_engine` / `llm_version`	string	no	Per-turn model override (e.g. multi-provider conversations).

Response — 201 Created

              {

                "id": "550e8400-e29b-41d4-a716-446655440000",

                "status": "created",   // "created" | "updated" | "duplicate"

                "message_count": 4

              }

curl example

curl -X POST https://chat.rewire2046.com/api/v1/collect \
  -H "X-API-Key: <your-client-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "page_url": "api://anthropic/my-script-conv-001",
    "source_domain": "api.anthropic.com",
    "conversation_title": "Draft email via Claude API",
    "llm_engine": "anthropic",
    "llm_version": "claude-opus-4",
    "metadata": {"origin": "api"},
    "qa_pairs": [
      {
        "sequence_number": 0,
        "question": "Draft a short thank-you email.",
        "answer": "Sure! Here is a draft ...",
        "message_date": "2026-09-03T10:00:00+08:00"
      }
    ]
  }'

Python example

import anthropic, requests, datetime, uuid

client = anthropic.Anthropic()

question = "Explain quantum entanglement in one paragraph."
resp = client.messages.create(
    model="claude-opus-4-5",
    max_tokens=512,
    messages=[{"role": "user", "content": question}],
)
answer = resp.content[0].text
conv_id = str(uuid.uuid4())
now = datetime.datetime.now(datetime.timezone.utc).isoformat()

requests.post(
    "https://chat.rewire2046.com/api/v1/collect",
    headers={"X-API-Key": "<your-client-key>"},
    json={
        "page_url": f"api://anthropic/{conv_id}",
        "source_domain": "api.anthropic.com",
        "conversation_title": question[:60],
        "llm_engine": "anthropic",
        "llm_version": resp.model,
        "metadata": {"origin": "api"},
        "qa_pairs": [{
            "sequence_number": 0,
            "question": question,
            "answer": answer,
            "message_date": now,
        }],
    },
).raise_for_status()

Connected Apps

Client	API Key	Requests	Conversations	Last Used	Status	Actions
No integrations yet

Authentication

Pass the API key in the X-API-Key header on every request. Client keys have access to all search and read endpoints. Only the master key can manage integrations (create / rotate / delete clients).