specllm
Makes any LLM behave like a regular REST API. Define the contract, specllm enforces it. The caller never knows an LLM is involved.
Every team shipping LLMs into production rebuilds the same layer: validation, retries, caching, error handling. specllm handles all of it from your API spec.
flowchart LR
A[Your App] -->|Request JSON| B[specllm]
B -->|Prompt| C[Any LLM]
C -->|Response| B
B -->|Validated JSON| A
Quick Start
pip install specllm
python -m specllm.demo # runs locally, no API key needed
Or with a real LLM:
pip install specllm[anthropic]
from specllm import SpecLLM
app = SpecLLM.from_openapi("./api.yaml") # provider inferred from spec
app.serve(port=8080)
Your spec declares the model:
info:
x-specllm-model: claude-sonnet-4-20250514
That's it. No provider class, no config.
Features
Model Selection via Spec
info:
x-specllm-model: claude-sonnet-4-20250514 # default for all endpoints
paths:
/v1/fast-route:
post:
x-specllm-model: claude-haiku-4 # override: cheap/fast
Built-in providers: Anthropic (claude-*) and OpenAI (gpt-*, o1-*, o3-*). Custom providers just implement one method:
class MyProvider(LLMProvider):
def call(self, prompt: str, system_prompt=None) -> str:
... # return raw text or dict — pipeline handles JSON extraction
Dynamic Response Constraints (x-constrain-from)
Let the caller control what the LLM can return — per request:
intent:
type: string
x-constrain-from: "intents" # enum pulled from request body field "intents"
score:
type: integer
x-constrain-from:
minimum: "min_score" # range pulled from request body
maximum: "max_score"
If the LLM picks outside the caller's options, specllm retries with feedback automatically.
Custom Validation & Prompts
@app.validate("/v1/route-ticket")
def only_enterprise(body):
if body.get("customer_tier") != "enterprise":
return "Only enterprise tickets accepted"
@app.prompt("/v1/answer")
def grounded_prompt(body):
return (
f"Answer ONLY from the following context. If the answer is not in the context, say so.\n\n"
f"Context:\n{body['context']}\n\n"
f"Question: {body['question']}"
)
Configuration (optional overrides)
app = SpecLLM.from_openapi("./api.yaml", config={
"timeout_seconds": 30,
"fallback_provider": backup_provider,
"cost_limit_daily": 50.0,
"cache_ttl": 3600,
})
Observability
Every response includes headers: X-SpecLLM-Request-Id, X-SpecLLM-Latency-Ms, X-SpecLLM-Tokens-Used, X-SpecLLM-Retries, X-SpecLLM-Cache-Hit.
Testing (no LLM credentials needed)
from specllm.testing.record_replay import RecordReplayProvider
# Record locally, replay in CI:
provider = RecordReplayProvider(provider=real_provider, cassette="tests/tape.json")
How It Works
flowchart TD
A[Request] --> B[Validate Input]
B -->|Invalid| C[400 Error]
B -->|Valid| D[Resolve Constraints]
D --> E{Cache Hit?}
E -->|Yes| F[Return Cached]
E -->|No| G[Build Prompt & Call LLM]
G --> H{Valid Output?}
H -->|Yes| I[Cache & Return]
H -->|No| J[Retry with Feedback]
J -->|Success| I
J -->|3x Failed| K[422 Error]
Error Handling
| Scenario | HTTP | Code |
|---|---|---|
| Bad input | 400 | INPUT_VALIDATION_FAILED |
| Output failed after retries | 422 | OUTPUT_SCHEMA_VIOLATION |
| Provider down/timeout | 503/504 | PROVIDER_UNAVAILABLE / PROVIDER_TIMEOUT |
| Cost limit hit | 503 | COST_LIMIT_REACHED |
All errors return structured JSON with code, status, message, request_id, timestamp.
License
Apache License 2.0
Metadata
Release files for specllm 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| specllm-0.1.2.tar.gz | 28.8 kB | With provenance | Details for specllm-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| specllm-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for specllm-0.1.2-py3-none-any.whl |
Total release size: 52.9 kB
Release files / specllm-0.1.2.tar.gz
| Download URL | specllm-0.1.2.tar.gz |
|---|---|
| Size | 28.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
070993060b118528688e28a27a84616884a016b4db8de597d13b595b5ff3ccca
|
|
BLAKE2b-256 checksum How to use checksums |
857594ee4ab8abaa4a84f355f65182e5840a80795be55031ee4c662de46fa2c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logRelease files / specllm-0.1.2-py3-none-any.whl
| Download URL | specllm-0.1.2-py3-none-any.whl |
|---|---|
| Size | 24.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1dec4fe30c3f581bb50d5f8eda5c150a17eb5419ec85370d1ad46886de6c04ad
|
|
BLAKE2b-256 checksum How to use checksums |
e3c1e17d2d0ed79cd69e7640857a205b87a5db840bafabdc5cde998da52317e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logSecurity for specllm 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for specllm-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.