Score Live Demo API
Create a locally issued key, call a real Score Live endpoint and inspect its actual JSON response. Synthetic demonstration data — not a third-party AI service.
No Google, Gemini, OpenRouter, Claude or Anthropic credential is created here. The endpoint does not run a language model and never proxies an external provider.
A transparent API lifecycle you can inspect
This demonstration is designed to show the mechanics around an API rather than pretend to offer generative intelligence. Registration creates a cryptographically random Score Live demo key. A keyed hash and short prefix are stored in private JSON Lines files outside the public web root; plaintext keys are not stored. When a valid active key calls the endpoint, the server returns a small type-specific sample that is deliberately labelled synthetic.
- Register
Submit limited contact details, a demo type and explicit consent. - Save the key
The plaintext credential is shown once in the current browser session. - Test responses
Use the workbench or an example request and handle real HTTP status codes.
What validation does—and does not—mean
The form rejects malformed, reserved, disposable and obvious placeholder email patterns, checks that the email domain publishes an MX or A record, and applies E.164-style and basic country-length checks to the phone number. It also rejects common repeated, sequential and dummy patterns. These are plausibility controls only. Without an OTP or verification email, they cannot prove that an address or phone number belongs to the visitor.
Privacy and retention
Registration records include the cleaned fields you submit, API type, consent version, timestamps, key prefix and hash, status, a salted hash of the requesting IP and a truncated user-agent. Usage logs exclude prompts and plaintext secrets. Operational guidance sets a default review-and-delete target of 90 days for usage logs and 180 days after revocation or inactivity for registrations, subject to legal and abuse-prevention needs. See the privacy policy and use the contact page for a privacy request.
Generate and manage a demo key
The key remains masked until registration succeeds. Generate and Copy open the same registration gate when no active key exists. Regeneration and revocation require both the current plaintext key and the browser session that created it.
Register to reveal a key. Copy it before leaving the page because it cannot be recovered.
Credential handling checklist
- Send the key through the
Authorization: Bearerheader, not a URL query string. - Do not commit it to source control, expose it in public client bundles or paste it into issue trackers.
- Regenerate after suspected exposure and update the secret in your application immediately.
- Revoke a key that is no longer required. Revoked requests receive an HTTP 403 response.
Quick Start
The examples below call the same internal endpoint used by the browser tester. Replace the placeholder after creating a key. Requests are JSON, use POST and include a prompt of 1–500 characters. The prompt influences only validation and sample metadata; no model processes it, and it is not written to usage logs.
Expected success envelope
A valid call receives HTTP 200 and a body containing status=success, demo=true, code=200, a unique request ID, UTC timestamp, API type, explanatory message and a compact synthetic data object. Integrations should inspect the HTTP status as well as the JSON body.
API Tester
This workbench sends a real same-origin request to /api/demo-call.php. Generate a key first; the response panel shows the actual status and JSON returned by PHP.
Generate a key, then send a request. The actual HTTP status and JSON response will appear here.
Documentation
Endpoint
POST /api/demo-call.php accepts same-origin requests with JSON or standard form data. Supply the key in Authorization: Bearer anna_demo_…. Cross-origin access is not enabled.
| Field | Requirement | Purpose |
|---|---|---|
api_type | Optional; must match the key when provided | One of llm-text, news-summary or sports-brief. |
prompt | Required, 1–500 characters | Exercises request validation. It is not logged or sent to a model. |
HTTP status contract
| Status | Meaning | Client action |
|---|---|---|
| 200 | Authenticated synthetic response | Read the response envelope and data object. |
| 400 | Malformed body or automated-form trap | Correct request formatting. |
| 401 | Missing, malformed or unknown key | Supply the current Score Live demo key. |
| 403 | Revoked key, type mismatch or CSRF/session failure on key actions | Do not retry unchanged; correct credentials or session. |
| 405 | Non-POST request | Use POST. |
| 413 | Request body above 16 KiB | Reduce request size. |
| 415 | Unsupported media type | Use JSON or standard form encoding. |
| 422 | Field validation failed | Read the field error and correct it. |
| 429 | Registration or call limit reached | Wait before retrying. |
| 503 | Temporary private-storage problem | Retry later; no success should be assumed. |
Security model and limits
Keys are generated with the operating system cryptographic random source and stored only as HMAC-SHA-256 hashes using a private pepper. JSON Lines updates use exclusive file locks and restrictive permissions. This design suits a modest shared-hosting demo, not high-throughput infrastructure. It has no database, distributed lock, model backend, uptime guarantee or external credential brokerage.
Frequently asked questions
Is this a real large language model API?
No. It is the Score Live Demo API. It validates a locally issued key and returns small, explicitly synthetic JSON examples. It never sends your prompt to a third-party model.
Does Score Live issue Google, OpenRouter or Anthropic credentials?
No. New Score Live demo keys begin with scorelive_demo_; previously issued keys keep working. Provider credentials must be obtained from each provider through its official process.
Why do I need to register?
Registration demonstrates a gated key-issuance flow and helps control abuse. The form applies format and plausibility checks, but there is no OTP or email verification and Score Live does not claim the details belong to the visitor.
Is my API key stored?
The plaintext key is returned once and is not written to storage. Score Live stores a keyed cryptographic hash and a short display prefix so calls can be authenticated and the dashboard can identify a record without exposing the key.
What data is logged for a demo call?
Usage records contain the time, key prefix and hash reference, API type, endpoint, HTTP status and a salted hash of the requesting IP. Prompts, plaintext keys and secrets are not written to usage logs.
What happens after I regenerate a key?
The previous hash is replaced through an append-only state event, so the old key receives an authentication error. The replacement plaintext key is displayed once.
What responses should my integration handle?
Successful calls use HTTP 200. Missing or unknown keys use HTTP 401, revoked or mismatched keys use HTTP 403, invalid request data uses HTTP 422, rate limits use HTTP 429, and temporary storage failures use HTTP 503.
Can I use this endpoint in production?
Use it only for learning, prototypes and integration checks. It has no model intelligence, service-level agreement or guaranteed long-term availability, and its synthetic samples must not be treated as factual content.
Need another answer? Review the API directory, terms or contact Score Live.