> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nephia.cc/llms.txt
> Use this file to discover all available pages before exploring further.

# X

> What a keyword captures on X, and what arrives in each event.

## Coverage

A keyword with X enabled polls a **search query** on your interval and keeps every tweet that matches. The query is X search syntax, so the same operators you would use in the app narrow a search: `from:handle`, `-filter:replies`, `"exact phrase"`, `lang:fr`.

A search can carry several terms at once, OR'd into one upstream request at one tick's cost. See [Keywords](/keywords).

| Criterion | Values | Default |
| - | - | - |
| `filters.queryType` | `Latest`, `Top` | `Latest` |

```bash theme={null}
curl -X POST https://api.nephia.cc/v1/keywords \
  -H "x-api-key: $NEPHIA_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "name": "Acme on X",
    "refreshIntervalSeconds": 900,
    "globalCriteria": { "market": "global", "terms": ["acme", "acme.com", "@acme"] },
    "sources": [{ "source": "x", "enabled": true }],
    "webhookUrl": "https://example.com/hooks/nephia"
  }'
```

Interval: **60 to 86400** seconds. At most **20** active X searches per Account.

## What an event carries

Each match is delivered as a `tweet.created` event with the full tweet: text, metrics, the author, and the media and links it carried. `webhookUrl` is optional: without it the keyword still records every match, readable through `GET /v1/keywords/{id}/events` in the same shape. See [Webhooks](/webhooks#replay).

### Verification fields

Author objects expose two separate flags:

* `verified` — legacy checkmark (government/brand/org verification before X Premium)
* `isBlueVerified` — X Premium / Blue subscription badge

Read both fields. They are not interchangeable.

## Billing

A tick costs **4 credits**, whatever the search returns. The two gestures that read a
whole page are charged on what that page returns instead, 5 credits plus 3 per tweet, so
at most 65 a page of 20: a [first scan](/keywords#backfill) reads one, and the dashboard's
60-day history up to five, at most 325. A search that matches nothing costs the 5. See
[Credits](/credits#polling).

## Limits

An author's likes are heavily restricted by X and are not a search criterion. Deleted and protected tweets stop appearing in matches rather than being retracted from a feed you have already read.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.