ChikoCorp · Authentication Profile

ChikoCorp Authentication

Authentication

ChikoCorp secures its APIs with apiKey, http, and x402 across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyArtificial IntelligenceCryptocurrencyx402PaymentsStablecoinsTRONRisk ScreeningDeveloper ToolsDiagnostics
Methods: apiKey, http, x402 Schemes: 3 OAuth flows: API key in: cookie, header

Security Schemes

browserSession apiKey
· in: cookie (__session)
bearerApiKey http
scheme: bearer
x402 x402-payment

Source

Authentication Profile

Raw ↑ 
generated: '2026-11-03'
method: searched
source:
- https://usdt.chikocorp.com/api-docs
- https://usdt.chikocorp.com/llms.txt
- openapi/chikocorp-com-tron-usdt-risk-openapi.yml
- openapi/chikocorp-com-x402-launch-verification-openapi.yml
docs: https://usdt.chikocorp.com/api-docs
summary:
  types:
  - apiKey
  - http
  - x402
  api_key_in:
  - cookie
  - header
schemes:
- name: browserSession
  type: apiKey
  in: cookie
  parameter: __session
  description: Clerk browser session; these /api endpoints use current-user ownership rather than machine API keys.
  sources:
  - openapi/chikocorp-com-tron-usdt-risk-openapi.yml
- name: bearerApiKey
  type: http
  scheme: bearer
  description: 'TRON Checker workspace API key sent as Authorization: Bearer. Docs: "Use a bearer API key with the screen:write
    scope." Live key prefix shown in the docs example: usk_live_. On x402 Launch Verification, the bearer token is the one
    returned in the case/monitor receipt.'
  key_prefix_live: usk_live_
  scopes_documented:
  - screen:write
  scopes_note: Docs say batch, reports, watchlist and webhooks "Use scoped bearer keys" but name no scope other than screen:write.
  sources:
  - openapi/chikocorp-com-tron-usdt-risk-openapi.yml
  - openapi/chikocorp-com-x402-launch-verification-openapi.yml
  - https://usdt.chikocorp.com/api-docs
- name: x402
  type: x402-payment
  description: 'Pay-per-request with no account or key: unpaid request receives HTTP 402 + PAYMENT-REQUIRED header; client
    retries with PAYMENT-SIGNATURE after authorizing USDC on Base. Used by POST /v1/x402/screen (usdt) and the paid x402 Preflight
    audit/remediation and Launch Verification routes.'
  quote: 'Auth: none (no Clerk, API key, or prepaid credits)'
  sources:
  - https://usdt.chikocorp.com/llms.txt
  - https://usdt.chikocorp.com/api-docs
  - https://x402.chikocorp.com/llms.txt

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/chikocorp-com-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.