AI Detection & Response Python-based SDK for monitoring agent workflows, language model execution, tool calls, and relevant data sources.
Features
- Automatic tracing: Works with any language model provider (OpenAI, Anthropic, custom)
- Zero code changes: Just initialize and go
- Comprehensive telemetry: Tracks tools, models, prompts, reasoning
- Simple API: 2 lines of code
Supported Frameworks
- OpenAI SDK
- Anthropic SDK
- Google (Gemini) SDK
- AWS Bedrock SDK
- Azure Foundry SDK
- LiteLLM SDK
- LangChain
Installation
pip install evoke-sdk
Quick Start
import evoke
# Initialize once at startup
evoke.init(api_key="evoke_pk_your_api_key")
# All LLM calls are now automatically traced!
from openai import OpenAI
client = OpenAI()
response = client.chat.completions.create(
model="gpt-4",
messages=[{"role": "user", "content": "Hello!"}]
)
What Gets Tracked
- Models: Which models were used (gpt-4, claude-3, etc.)
- Prompts & Responses: Full input and output data
- Tools: Which tools/functions were called
- Data Sources: Which vector stores/retrievers were accessed
- Tokens: Input/output/cached token counts
- Timing: Duration and timestamps
- Errors: Exceptions and stack traces
Optional: Explicit Tracing
Use the @guard decorator for high-level workflows:
@evoke.guard(name="customer_support_agent")
def handle_customer_query(query: str):
# Your agent logic
return agent.run(query)
Optional: Add Custom Context
Link custom business values to track custom events and create custom detections:
@evoke.guard(name="process_order")
def process_order(order_id: str, user_id: str):
evoke.add_context(
user_id=user_id,
order_id=order_id,
environment="production"
)
return process()
Flush Before Exit
Ensure all data is sent before your app exits:
# At the end of your script
evoke.flush()
Metadata
Release files for evoke-sdk 0.2.0
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 |
|---|---|---|---|---|
| evoke_sdk-0.2.0.tar.gz | 18.4 kB | Without provenance | Details for evoke_sdk-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| evoke_sdk-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for evoke_sdk-0.2.0-py3-none-any.whl |
Total release size: 39.2 kB
Release files / evoke_sdk-0.2.0.tar.gz
| Download URL | evoke_sdk-0.2.0.tar.gz |
|---|---|
| Size | 18.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33c24e9e045415e5992c9f245a90ffb7a728aced955e0d39ecb2c7a3c320d652
|
|
BLAKE2b-256 checksum How to use checksums |
b25093e64b1d20f654023e5229130e99649cde248361a83f12fa1c5966cee816
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / evoke_sdk-0.2.0-py3-none-any.whl
| Download URL | evoke_sdk-0.2.0-py3-none-any.whl |
|---|---|
| Size | 20.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5895fbeeb614b7fcf8bba96a94e86a049bc17a9ad7ed3d06a6ae9db4346e8cac
|
|
BLAKE2b-256 checksum How to use checksums |
9ff9526dce95c5ba02b12e377717316cddb342ca1bf8f9d8443bfef3a4e34aa2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for evoke-sdk 0.2.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
