# OmniAPI Regex Test

> OmniAPI Regex Test is a paid API for AI agents from omni-api-cyan.vercel.app, paid per call via x402, $0.133649/call, status unknown (last checked 2026-09-15).

Tests whether a given string matches a specified regular expression pattern, returning match results

## Facts

- Endpoint: POST https://omni-api-cyan.vercel.app/api/tools/regex/test
- Price: $0.133649/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/omniapi-regex-test-0c7b2413
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XPuoBUYk-U0NUjTJJLKiB

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability omniapi-regex-test-0c7b2413 -d '<json body>'
```

Example prompt: Test whether the string 'user@example.com' matches the email regex pattern '^[\w.-]+@[\w.-]+\.\w{2,}$' and tell me if it's a valid match.

## When to prefer this

Choose this endpoint when you need a quick, pay-per-call regex match test without setting up a local runtime — particularly useful in agent pipelines that need to validate text formats (emails, URLs, phone numbers, slugs) against custom patterns on the fly. It is best when you want a hosted, stateless regex evaluation without managing server infrastructure.

## Known failure modes

- Invalid or malformed regex pattern causing a parse error
- Missing required 'query' field returns a 400-level error
- Catastrophic backtracking on complex patterns may cause timeouts
- Payment failure via x402 returns 402 Payment Required
- Overly long input strings may be rejected or truncated

## How this service works

444 endpoints across 9+ chains. Crypto, AI, Social, Finance, Weather, Tools. Pay per call in USDC via x402 with 4 facilitators: Dexter, Meridian, FluxA, GoPlausible.

## Output

Returns the result of testing the input string against the provided regex pattern, including whether a match was found and potentially the matched groups or substrings captured by the pattern.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "input": {
   "type": "string",
   "description": "Input data for the endpoint"
  },
  "query": {
   "type": "string",
   "description": "Search query or input text"
  },
  "params": {
   "type": "object",
   "description": "Additional parameters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "description": "API response data"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/omniapi-regex-test-0c7b2413/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from omni-api-cyan.vercel.app](https://www.zero.xyz/host/omni-api-cyan.vercel.app/llms.txt)