Customer access beta

Enroll your organization and request a scoped documentation grant from one account.

Open your account, sign in with Google, and complete account setup. Your authenticated membership determines the organization; requests cannot select a different organization. Enrollment and free documentation grants do not make a payment.

AgentScore: private credential activity

Choose the enrollment action in your account. The account request uses your Klisten account session token (issued after Google sign-in), not an API key. Its body must be an empty JSON object.

POST https://api.klisten.co.kr/v1/account/agentscore/enroll
Origin: https://klisten.co.kr
Authorization: Bearer <Klisten-account-session-access-token>
Content-Type: application/json

{}

Enrollment enables the configured activity authority for your organization. It does not create a score or an activity record. To issue a record for an eligible paid ToolGuard observation, use the same API key associated with that observation and grant it agents:write. Reading requires agents:read.

POST https://api.klisten.co.kr/v1/agentscore/activity
Authorization: Bearer <Klisten-API-key>
Content-Type: application/json

{"scan_job_id":"<eligible-scan-job-UUID>"}

GET https://api.klisten.co.kr/v1/agentscore/activity/<eligible-scan-job-UUID>
Authorization: Bearer <Klisten-API-key>

Records are private to the authorized organization and credential. They describe observed activity, not independent quality, agent identity, reputation, or future reliability. An arbitrary scan identifier or another API key does not establish eligibility.

ClearGate: free documentation grants

Read the documentation license. In your account, choose internal reading or internal summarizing, select your actual supported two-letter territory, and explicitly accept the terms before requesting a grant. The service currently covers only Klisten-authored API documentation at https://klisten.co.kr/docs.html.

The account configuration at GET /v1/account/config exposes cleargate_customer_offer with the current terms URL, SHA-256 digest, and expiry. Submit that exact accepted digest. Use one unique idempotency key per request and reuse the same key and body if the response is uncertain.

POST https://api.klisten.co.kr/v1/account/cleargate/grants
Origin: https://klisten.co.kr
Authorization: Bearer <Klisten-account-session-access-token>
Content-Type: application/json
Idempotency-Key: <unique-16-to-128-character-key>

{
  "accepted_terms_sha256":"sha256:<accepted-offer-digest>",
  "purpose":"api-docs-read",
  "territory":"KR"
}

Use api-docs-summarize for internal summaries. A new request returns HTTP 201; recovery of the same request returns HTTP 200. The response contains grant_id, expires_at, reused, and permission_granted:false. Issuance alone is not authorization.

Before every use, call the check endpoint with a Klisten API key carrying content:check. The purpose must match your grant.

POST https://api.klisten.co.kr/v1/cleargate/check
Authorization: Bearer <Klisten-API-key>
Content-Type: application/json

{
  "grant_id":"<issued-grant-UUID>",
  "intent":{
    "publisher_id":"klisten-inc",
    "resource":"https://klisten.co.kr/docs.html",
    "audience":"klisten-cleargate-docs-v1",
    "purpose":"api-docs-read",
    "territory":"KR",
    "redistribute":false
  }
}

Proceed only when the current check returns AUTHORIZED, within its evaluated scope and expiry. A denied, expired, revoked, unavailable, or missing grant does not grant permission. The check evaluates current evidence; it does not fetch content or guarantee a later check will produce the same result.

Grants are free, last at most 30 minutes, and are limited to five active grants and 48 issued grants per organization per day. This beta provides no third-party publisher rights, redistribution, model-training rights, payment, or content delivery.

Keep credentials private

Use Klisten account session tokens only for account operations and scoped Klisten API keys for service calls. Do not place either token in public code or share it in support messages. For access questions, contact [email protected].