Tag Requests

Supported endpoints accept an optional tags input that gets recorded on the request’s usage log. Tags are yours to define — common uses are environment (production, staging), team or tenant (team-alpha, customer-42), or feature (onboarding-flow, nightly-refresh). You can then filter the usage tab of your dashboard by any tag to see credits burned by that slice. Tags are purely for observability. They don’t change response shape, pricing, caching, or rate limits.

When to use tags

Reach for tags when a single API key serves multiple workloads and you need to see which one is spending credits:

Split spend between production and staging on the same key.
Attribute usage to internal teams, tenants, or customers.
Compare cost of one code path (say, nightly-batch) against another (user-triggered).
Track cost of an experiment or migration before you commit.

If everything on the key is one workload, you don’t need tags.

How to send tags

Tags are optional only where the endpoint’s API reference lists a request-level tags field. GET /v1/batch/{batch_id}, DELETE /v1/batch/{batch_id}, GET /v1/batch/{batch_id}/results, and POST /v1/batch/{batch_id}/cancel do not accept request tags. On batch submission and monitors, tags instead belong to the created resource; GET /v1/batch/list uses tags only to filter batches. The shape depends on the HTTP method:

Request type	Where tags go	Format
`POST` (JSON body)	`tags` field in the body	Array of strings
`GET` and `POST /v1/parse`	`tags` query parameter	Comma-separated string

For query parameters, send one comma-separated tags value. Do not repeat the parameter. Limits (same as monitor tags):

Up to 20 tags per request.
Each tag is 1–50 characters.
Invalid tags return 400 INPUT_VALIDATION_ERROR.

POST example

curl -X POST https://api.context.dev/v1/brand/retrieve \
  -H "Authorization: Bearer $CONTEXT_DEV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "by_domain",
    "domain": "stripe.com",
    "tags": ["production", "team-alpha"]
  }'

const { brand } = await client.brand.retrieve({
  type: "by_domain",
  domain: "stripe.com",
  tags: ["production", "team-alpha"],
});

brand = client.brand.retrieve(
    type="by_domain",
    domain="stripe.com",
    tags=["production", "team-alpha"],
)

GET example

cURL

curl "https://api.context.dev/v1/web/scrape/markdown?url=https://example.com&tags=production,team-alpha" \
  -H "Authorization: Bearer $CONTEXT_DEV_API_KEY"

Filter usage by tag

Once a tagged request is logged, open the usage tab of your dashboard and filter by any tag to see the credits and request count attributed to that slice. Monitor runs on a monitor that has resource-level tags also appear under those tags, so you can view monitor and non-monitor spend side by side.

Handle Rate Limits — pace requests once you’ve identified which tag is burning quota.
Best Practices — patterns to keep spend predictable.

Get Started

Give it to your Agent

What can Context.dev do

Optimizations

Integrations

When to use tags

How to send tags

POST example

GET example

Filter usage by tag

​When to use tags

​How to send tags

​POST example

​GET example

​Filter usage by tag

​Related

When to use tags

How to send tags

POST example

GET example

Filter usage by tag

Related