grepture.com valid

Grepture

Grepture is an AI gateway for securing and observing LLM API traffic. It works with OpenAI, Anthropic, Google, Azure, and any OpenAI-compatible provider — giving you PII redaction, cost tracking, observability, prompt management, evals, and request control from a single SDK.

For agents: AI gateway for LLM API traffic offering PII redaction, cost tracking, observability, prompt versioning, evals and provider routing via a single SDK.

llm gatewaypii redactionllm observabilitycost trackingprompt management

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T18:21:10.514Z. Cached copy · Source on grepture.com

# Grepture

> Grepture is an AI gateway for securing and observing LLM API traffic. It works with OpenAI, Anthropic, Google, Azure, and any OpenAI-compatible provider — giving you PII redaction, cost tracking, observability, prompt management, evals, and request control from a single SDK.

The SDK supports two operating modes:

- **Proxy mode** (default) — requests route through the Grepture proxy, where detection rules run before traffic reaches the provider. Use this for PII redaction, request blocking, mask-and-restore, and prompt management.
- **Trace mode** — requests go directly to the LLM provider with zero proxy overhead. The SDK captures metadata (model, tokens, latency, cost) asynchronously and sends it to the dashboard. Use this for observability and cost tracking on latency-sensitive workloads.

Both modes share the same dashboard: traffic log, cost tracking, conversation tracing, evals, and reports.

## Core Concepts

- **Proxy mode**: A reverse proxy that intercepts AI API calls, applies detection rules, and forwards cleaned requests
- **Trace mode**: Direct-to-provider requests with async metadata capture — same dashboard visibility, zero latency overhead
- **Rules**: Configurable detection and action policies (detect PII, block prompt injections, redact fields, etc.)
- **Mask & Restore**: Tokenize sensitive values on the way out, restore them on the way back
- **Cost tracking**: Per-request token counts and cost attribution across all providers
- **Conversation tracing**: Group related requests by trace ID to see multi-step workflows end to end
- **Prompt management**: Version, manage, and deploy prompts server-side via API — no redeployments needed
- **Evals**: LLM-as-a-judge evaluation on your traffic logs with pre-built templates and custom judge prompts
- **Prompt A/B testing**: Split traffic between prompt versions, measure eval scores per version, and activate the winner — zero code changes needed
- **OpenTelemetry integration**: Export traffic as OTLP traces to Datadog, Grafana, Honeycomb, or any observability platform
- **Reports**: PDF export of cost, traffic, and GDPR compliance reports
- **CLI**: Local AI gateway via `npx @grepture/proxy` for development and self-hosted deployments
- **Zero-Data Mode**: When enabled, no request or response bodies are stored in traffic logs
- **SDK**: A TypeScript drop-in wrapper (`@grepture/sdk`) that works in both proxy and trace mode

## How It Works

### Proxy mode (default)

1. Your app sends an LLM API request through the Grepture proxy (via the SDK or direct HTTP)
2. The proxy scans the request against your configured rules
3. Matching rules trigger actions: redact PII, tokenize fields, block the request, or log-only
4. The cleaned request is forwarded to the LLM provider
5. The response is scanned with output rules, detokenized (restoring original values), and returned

### Trace mode

1. Your app sends the LLM API request directly to the provider — no proxy in the path
2. The SD
…

Related sites

Other listed sites in AI agents and MCP. See the whole category →

Machine-readable: GET /v1/resolve?q=grepture.com · GET /v1/domain/grepture.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for grepture.com:
1. POST https://agentwebmap.com/v1/sites/grepture.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://grepture.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/grepture.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/grepture.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.