Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.lemondata.cc/llms.txt

Use this file to discover all available pages before exploring further.

​
Path Parameters

​
model
string
required
The ID of the model to retrieve (e.g., gpt-5.4, claude-sonnet-4-6).

​
Response

​
id
string
Model identifier.
​
object
string
Always model.
​
created
integer
Creation timestamp.
​
owned_by
string
Model provider.
​
lemondata
object
LemonData-specific public metadata. The detail route can include category, pricing_unit, capability_flags, supported_operations, pricing_provenance, public_contract_summary, the full public_contract, and scene-level agent_preferences for non-chat recommendation snapshots.
curl "https://api.lemondata.cc/v1/models/gpt-5.4" \
  -H "Authorization: Bearer sk-your-api-key"

{
  "id": "gpt-5.4",
  "object": "model",
  "created": 1706000000,
  "owned_by": "openai"
}

​
Error Handling

If the model doesn’t exist, you’ll receive a 404 error: 
{
  "error": {
    "message": "Model 'invalid-model' not found",
    "type": "invalid_request_error",
    "code": "model_not_found"
  }
}

​
Non-Chat Recommendation Metadata

For non-chat models, the detail route also returns lemondata.agent_preferences.<scene>. Use it to inspect:
  • preferred_rank
  • success_rate_24h
  • sample_count_24h
  • status
  • updated_at
The public response intentionally keeps basis.channel_id and basis.physical_model as null so agents can consume the recommendation signal without learning internal routing identifiers.

​
Public Detail Metadata

Compared with GET /v1/models, the detail route can additionally return:
  • lemondata.capability_flags
  • lemondata.supported_operations
  • lemondata.pricing_provenance
  • lemondata.public_contract_summary
  • lemondata.public_contract