> ## Documentation Index > Fetch the complete documentation index at: https://docs.fiddler.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get the evaluator rules that use a provider's models and credentials > For each of the provider's models and credentials, the evaluator rules in the organization whose current evaluator uses it. Requires LLM Gateway Management Update: it serves the warnings before a delete or an edit, for those who can make those changes. Read this before deleting the provider, or removing a model or credential from it, to warn the user. While rules use them, the delete or update is refused with a `409` unless `acknowledge_usage=true` is sent. Archived evaluator versions, and evaluators that no rule uses, are not counted. `total` counts every affected rule in the organization. `items` lists at most 10, only from projects where the caller can read the rule, its application and its evaluator. Rules in other projects are only counted, in `hidden` and `hidden_projects`; their names are never returned. Rules beyond the cap number `total - hidden - len(items)`. ## OpenAPI ````yaml GET /v3/llm-gateway/providers/{provider}/usage openapi: 3.0.3 info: title: Fiddler API - 2.0 description: APIs to interact with Fiddler termsOfService: https://fiddler.ai/about/terms contact: email: support@fiddler.ai license: name: Proprietary url: '2.0' version: '2.0' servers: [] security: - BearerAuth: [] tags: - name: access-key description: CRUD operations for API keys - name: agent-v3 description: CRUD for the Agent Registry (Stage 1, manual entries) - name: aggregation-invalidation-request-v3 description: Endpoints related to retrieving aggregation invalidation requests - name: alert-rules-v3 description: CRUD for Alert Rules, Summary, and Stats APIs - name: application-v3 - name: auth description: Authentication strategies and login flows - name: baseline-v3 description: CRUD for baseline - name: catalog-v3 description: >- Entity catalog provides paginated, searchable discovery of entity names (attribute keys, agent names, span types, span names, score names, evaluator config names) and their distinct values. Powered by ClickHouse materialized views — no worker or PostgreSQL dependency. - name: chart-annotation-v3 description: Endpoints related to retrieving chart annotations - name: chart-v3 description: CRUD for chart - name: queries-v3 description: v3 queries API - name: configuration-v3 description: > Read and change runtime configurations (Config Manager) for your organization, its projects, and its models. **Private preview.** These endpoints accept requests on every deployment. Whether a saved value takes effect depends on two deployment settings that are off by default: one makes Fiddler read stored values, and the other runs the configuration worker, which applies retention changes to stored data. Contact your Fiddler Customer Success Manager before using these endpoints. This reference documents the data retention (TTL) settings: `PROD_EVENTS_TTL_DAYS`, `GENAI_TRACES_TTL_DAYS`, and `GENAI_METRICS_TTL_DAYS`. The API accepts other registered settings too; contact your Fiddler Customer Success Manager before changing any of them. **Retention settings permanently delete data** once it is older than the configured period. When existing data is affected depends on the setting; see each setting's description. - name: cost-evaluators-v3 description: > Paginated roll-up of per-evaluator LLM cost and token usage, aggregated hourly. Available only on deployments with evaluator cost reporting enabled. - name: custom-metrics-v3 - name: dimensionality-reduction-v3 - name: environment-v3 description: Endpoints related to environment management - name: evals - name: datasets - name: evaluation-v3 - name: evaluator-v3 - name: rule-evaluators-v3 - name: experiment-v3 - name: explainability-v3 - name: llm_rca-v3 - name: file-upload description: Endpoints related to file uploading. - name: fql-expressions-v3 description: > Endpoints for listing FQL (Fiddler Query Language) functions available for GenAI custom metrics. Used by the frontend for autocomplete and signature hints in the FQL editor. - name: genai-alert-rules-v3 description: CRUD API for GenAI Alert Rules - name: genai-custom-metrics-v3 description: API for GenAI Custom Metrics - name: genai-filters-v3 description: API for GenAI Filters - name: genai-metrics-v3 description: >- Endpoints for pre-aggregated GenAI metrics. All metric data is pre-aggregated hourly by a Celery-based metric collector; no real-time aggregation is performed at request time. - name: guardrails-api description: Endpoints related to retrieving Guardrails specific data - name: ingestion-v3 - name: intercom-api description: Endpoints related to intercom APIs - name: jobs-v3 - name: llm-gateway-v3 - name: auth-login - name: auth-logout - name: mcp-client-setup-v3 description: Endpoints for retrieving MCP client setup instructions. - name: metrics-v3 description: Metrics endpoints - name: model-v3 - name: dashboard-v3 - name: model-deployment-v3 - name: monitoring-summary-v3 - name: histograms-v3 - name: organization-roles-v3 description: Update user org role - name: organization-settings-v3 description: Update organization settings such as timezone, email configuration, etc. - name: pagerduty-api description: CRUD for Pagerduty services. - name: project-v3 - name: project-roles-v3 description: Project role assignment management - name: scores-v3 description: Unified CRUD for scores and annotations - name: searchable-text-key-v3 description: >- Manage the global searchable text keys table that controls which OTel attribute keys are routed to the full-text-searchable `ValueContent` column in the unified attributes table. Changes propagate to the backing ClickHouse dictionary within 1-2 minutes and affect all tenants. - name: segments-v3 - name: semantic-mapping-v3 description: >- Manage the global semantic name mappings table that maps raw OTel attribute keys to canonical semantic concepts. Changes propagate to the backing ClickHouse dictionary within 1-2 minutes and affect all tenants. - name: server-info-v3 description: Endpoints related to retrieving server information - name: service-account description: > Service accounts and their API keys. A human Org Admin manages the service accounts of their own organization: create, read, update, and enable/disable (there is no delete — an account is disabled instead), and issue, rename, enable/disable, and revoke each account's API keys (a key's expiry is fixed at creation and changed only by rotating the key). An API key is an `fks_` secret that inherits the account's grants and cannot manage service accounts; an active, unexpired key must be disabled before it can be revoked, and it authenticates only while both it and its account are active. Scopes here are capability scopes (what the account may do), not OAuth scopes. - name: sessions-v3 description: v3 session APIs - name: span-v3 - name: team-roles-v3 - name: team-v3 - name: traces-v3 description: v3 trace api for monitoring - name: fetch-sessions-v3 description: v3 fetch sessions api for monitoring - name: user-access-key description: > CRUD operations for user API keys. All endpoints are user-scoped — each user can only operate on their own API keys. No one including Org admins have access to other users' API keys. - name: users-v3 - name: version-compatibility-v3 - name: webhooks externalDocs: url: https://docs.fiddler.ai description: Find out more about Fiddler paths: /v3/llm-gateway/providers/{provider}/usage: get: tags: - llm-gateway-v3 summary: Get the evaluator rules that use a provider's models and credentials description: > For each of the provider's models and credentials, the evaluator rules in the organization whose current evaluator uses it. Requires LLM Gateway Management Update: it serves the warnings before a delete or an edit, for those who can make those changes. Read this before deleting the provider, or removing a model or credential from it, to warn the user. While rules use them, the delete or update is refused with a `409` unless `acknowledge_usage=true` is sent. Archived evaluator versions, and evaluators that no rule uses, are not counted. `total` counts every affected rule in the organization. `items` lists at most 10, only from projects where the caller can read the rule, its application and its evaluator. Rules in other projects are only counted, in `hidden` and `hidden_projects`; their names are never returned. Rules beyond the cap number `total - hidden - len(items)`. operationId: getLLMProviderUsageV3 parameters: - $ref: '#/components/parameters/provider' responses: '200': description: The evaluator rules that use each model and credential content: application/json: schema: allOf: - $ref: '#/components/schemas/ApiResponse' - type: object properties: data: $ref: '#/components/schemas/ProviderUsage' examples: success: summary: One model used by a rule, and an unused credential value: api: v3 data: models: - uuid: 550e8400-e29b-41d4-a716-446655440000 name: gpt-4o affected: total: 1 hidden: 0 hidden_projects: 0 items: - application: id: 6f1c1c4e-4a7a-4e0e-9d0b-0b9a1c2d3e4f name: Support Bot evaluator_rule: id: 7a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d name: coherence-prod enabled: true evaluator: id: 8b3c4d5e-6f7a-4b8c-9d0e-1f2a3b4c5d6e name: Coherence judge credentials: - uuid: 9c4d5e6f-7a8b-4c9d-0e1f-2a3b4c5d6e7f name: prod-key affected: total: 0 hidden: 0 hidden_projects: 0 items: [] '403': $ref: '#/components/responses/403' '404': $ref: '#/components/responses/404' '500': $ref: '#/components/responses/500' components: parameters: provider: name: provider in: path description: Name of the LLM provider (e.g., OpenAI, Anthropic) required: true schema: type: string schemas: ApiResponse: type: object description: | Response object for standard API responses. properties: api_version: type: string default: '3.0' enum: - '2.0' - '3.0' description: | API version. kind: type: string default: NORMAL enum: - NORMAL description: | Type of response, indicating a normal response. ProviderUsage: type: object title: Provider Usage description: >- The evaluator rules that use each of a provider's models and credentials. required: - models - credentials properties: models: type: array items: $ref: '#/components/schemas/GatewayRowUsage' credentials: type: array items: $ref: '#/components/schemas/GatewayRowUsage' GatewayRowUsage: type: object title: Gateway Row Usage description: One model or credential and the evaluator rules that use it. required: - uuid - name - affected properties: uuid: type: string format: uuid name: description: The model name, or the credential name type: string affected: type: object properties: total: description: >- Every affected rule in the organization, including those not listed in `items` type: integer hidden: description: >- Affected rules in projects where the caller cannot read the rule, its application or its evaluator. Counted only; never listed. type: integer hidden_projects: description: The number of distinct projects the `hidden` rules belong to type: integer items: description: >- At most 10 affected rules, from projects where the caller can read the rule, its application and its evaluator type: array items: $ref: '#/components/schemas/GatewayRowUsageItem' required: - total - hidden - hidden_projects - items ErrorResponse: type: object description: | Response object for errors returned by the API. properties: api_version: type: string default: '3.0' enum: - '2.0' - '3.0' description: | API version of the response. kind: type: string default: ERROR enum: - ERROR description: | Type of response, usually indicating an error. error: type: object properties: code: type: integer format: int32 description: > Represents the code for this error, typically an HTTP response code. default: 400 enum: - 400 - 401 - 403 - 404 - 409 - 410 - 422 - 429 - 500 - 501 - 503 message: type: string description: > A human-readable message providing more details about the error. If there are multiple errors, it will be the message for the first error. example: Resource Not Found errors: type: array description: > Container for additional information regarding the error, especially for multiple errors. items: type: object properties: reason: type: string description: > Unique identifier for this error, different from the error code. example: ResourceNotFoundException message: type: string description: > A human-readable message providing more details about the error. If there is only one error, this field will match error.message. example: Resource Not Found help: type: string description: > Link to support or documentation providing more information on the error. GatewayRowUsageItem: type: object title: Gateway Row Usage Item required: - application - evaluator_rule - evaluator properties: application: $ref: '#/components/schemas/IdAndName' evaluator_rule: type: object properties: id: type: string format: uuid name: type: string enabled: type: boolean required: - id - name - enabled evaluator: description: >- The evaluator, identified by its entity id, which is stable across versions allOf: - $ref: '#/components/schemas/IdAndName' IdAndName: type: object required: - id - name properties: id: type: string format: uuid name: type: string responses: '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Resource not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: BearerAuth: type: http scheme: bearer ````