What makes etix-fpx notable?

1.3K downloads. Trust evidence available

How should etix-fpx be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

etix-fpx

Query etix.com (event ticketing) from a shell with the fpx CLI (@fetchproxy/cli) instead of running the etix-mcp server — search events, venues, and performers, and pull event/venue detail, via one-shot calls through a signed-in browser tab. Use when you want Etix discovery data without the MCP, in a script, or on a machine where the MCP isn't installed.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.3k

Updated

Oct 10, 2026

Version

1.1.7

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.3K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.3K downloadsadoption · observed Oct 10, 2026
Latest release: 1.1.7release · observed Oct 9, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17cjx1a349nz5apaqp02vgz4h85728z:etix-fpx

Install using `clawhub skill install s17cjx1a349nz5apaqp02vgz4h85728z:etix-fpx` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/chrischall/etix-fpx before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-chrischall-etix-fpx/snapshot"

Documentation

CLAWHUB

147,203 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: etix-fpx
description: >-
  Query etix.com (event ticketing) from a shell with the fpx CLI
  (@fetchproxy/cli) instead of running the etix-mcp server — search events,
  venues, and performers, and pull event/venue detail, via one-shot calls
  through a signed-in browser tab. Use when you want Etix discovery data
  without the MCP, in a script, or on a machine where the MCP isn't
  installed.
---

# Etix via fpx (no MCP)

Etix fronts its whole consumer surface (`www.etix.com/ticket/...`) with a
**DataDome** bot-wall that 403s/202s any plain `curl`/Node request
(`captcha-delivery` interstitial). `fpx` routes the request through the
user's own signed-in browser tab (the ContextMint Bridge extension), which has
already cleared DataDome, so the same request succeeds. No Etix account is
needed — this is public event-discovery data.

Etix also publishes a documented OpenAPI seller API (`api.etix.com/v3`),
but every endpoint requires OAuth2 password-grant with venue/box-office
credentials — it's out of reach for a consumer and out of scope here.

This is the same data the `etix_*` MCP tools return, reached with one CLI
call instead of a running server.

## One-time setup

```sh
npm install -g @fetchproxy/cli              # provides `fpx`
fpx profile add etix --domain etix.com      # only the fetch capability is needed
fpx pair -p etix                            # prints a pair code → approve in ContextMint Bridge
```

Requirements: the **ContextMint Bridge** browser extension installed
(from https://github.com/nullnet-app/contextmint-bridge/releases — the fetchproxy
extension under its new name, same maintainer, as https://github.com/chrischall/fetchproxy#extension
says; verify the zip with `shasum -a 256 -c <zip>.sha256` or build from source), with an open
`www.etix.com` tab that has finished loading (so the DataDome check
clears), and Chrome **Site access** allowing `etix.com`. Pairing persists —
after the first approval every later `fpx` call reuses it.

## Core call pattern

Two response shapes, both fetched with the plain `get` verb:

```sh
# Clean JSON — pipe straight to jq
fpx get 'https://www.etix.com/ticket/api/online/search/suggest?keywords=jazz' -p etix \
  | jq '.'

# Server-rendered HTML — save it, then pull the embedded JSON-LD/microdata
fpx get 'https://www.etix.com/ticket/p/39004863' -p etix > /tmp/event.html
```

A `POST` (only `geolocation/search` needs one) uses `post-json`:

```sh
printf '{"cityOrPostalCode":"Charlotte, NC","country":"USA"}' > /tmp/geo.json
fpx post-json 'https://www.etix.com/ticket/api/online/geolocation/search' @/tmp/geo.json -p etix \
  | jq '.'
```

Ready-to-run paths + extraction recipes (JSON `jq`, HTML JSON-LD/microdata
via a small `node` one-liner, and the page's `dataLayer` analytics object
via `references/extract-datalayer.mjs` — the same shapes `etix-mcp`'s
`src/parse.ts` parses) are in `references/etix-endpoints.md`.

## The one rule: resolve ids first

Event/venue detail take a numeric id, never

_meta.json

{
  "ownerId": "kn700jq4sjtf2anb0rk3ft4p7n856872",
  "slug": "etix-fpx",
  "version": "1.1.7",
  "publishedAt": 1791588249234
}

references/etix-endpoints.md

# Etix consumer endpoints for fpx

Ready-to-run request paths for
`fpx get|post-json 'https://www.etix.com<path>' -p etix`. All paths, field
names, and shapes are transcribed from `etix-mcp`'s `docs/ETIX-API.md` and
`src/parse.ts` — live-verified 2026-06-12 against venue `17987` (Middle C
Jazz Club) and performance `39004863` (NC Jazz Festival). Nothing here is
guessed.

Endpoint host: `https://www.etix.com`. Auth: none — every call still rides
the fetchproxy bridge because the whole zone sits behind DataDome, not
because these routes need an Etix account.

---

## 1. Search — `GET /ticket/api/online/search/suggest?keywords=<kw>` (do this first)

Clean JSON. Returns matching venues, events (performances), and performers.
Use this to resolve a name to an id before calling event/venue detail.

```sh
fpx get 'https://www.etix.com/ticket/api/online/search/suggest?keywords=jazz' -p etix > /tmp/suggest.json
jq '.' /tmp/suggest.json
```

Shape:

```jsonc
{
  "keywords": "jazz",
  "venues":     [ { "venueId": 17987, "venueName": "...", "organization": "...",
                    "address": "...", "city": "...", "state": "...", "country": "USA",
                    "venueSaleUrl": "/ticket/v/17987/middle-c-jazz-club" } ],
  "events":     [ { "eventId": 39004863, "eventName": "...", "categoryName": "Concerts",
                    "dateTime": "2027-02-05T00:30:00Z", "venueId": 4332, "venueName": "...",
                    "city": "...", "state": "...", "imageUrl": "https://cdn.etix.com/...",
                    "directSaleUrl": "/ticket/p/39004863/..." } ],
  "performers": [ { "id": 103251, "name": "Marion Meadows", "muzookaId": "mzoMB0Ym8l",
                    "imageUrl": "https://www.etix.com/ticket/api/online/search/muzooka/.../image" } ]
}
```

`performers` uses `id`/`name` — NOT `artistId`/`artistName` — and only
populates on a close artist match.

```sh
jq -r '.events[]     | "\(.eventId)\t\(.eventName)\t\(.dateTime)"' /tmp/suggest.json
jq -r '.venues[]     | "\(.venueId)\t\(.venueName)\t\(.city), \(.state)"' /tmp/suggest.json
jq -r '.performers[] | "\(.id)\t\(.name)"' /tmp/suggest.json
```

**Do NOT use** `POST /ticket/api/online/search` (the full-text search) — it
returns an encrypted/opaque payload, not JSON.

---

## 2. Event detail — `GET /ticket/p/<eventId>` → SSR HTML

The bare numeric id resolves without the URL slug. No clean JSON endpoint
exists; the page carries a schema.org **JSON-LD `Event`** block (sometimes
nested under `WebPage.mainEntity`) plus a single-quoted `dataLayer`
analytics object and an `og:image` meta tag.

```sh
fpx get 'https://www.etix.com/ticket/p/39004863' -p etix > /tmp/event.html
```

Extract the JSON-LD (it's real JSON once pulled out of the `<script>` tag —
pipe straight to `jq`):

```sh
node -e '
  const html = require("fs").readFileSync("/tmp/event.html", "utf8");
  const blocks = [...html.matchAll(/<script type="application\/ld\+json">([\s\S]*?)<\/script>/g)];
  for (const b of blocks) {
    const doc = JSON.pars

skill-card.md

## Description:

Guides agents to search public Etix events, venues, and performers and retrieve event and venue details through the fpx browser bridge instead of an MCP server.

This skill is ready for commercial/non-commercial use.

## Publisher:

[chrischall](https://clawhub.ai/user/chrischall)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and other agents use this skill to find public Etix events and venues from shell workflows without running the Etix MCP server.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The browser bridge grants fetch access and retains a local fpx pairing.

Mitigation: Limit the bridge profile to etix.com, verify the extension and package sources, and review the persistent pairing before installation.

Risk: Use in a logged-in session could expose account or purchase actions beyond public event lookup.

Mitigation: Restrict use to anonymous Etix discovery; do not use the skill for purchases or logged-in account actions.

## Reference(s):

- [Etix consumer endpoints and extraction recipes](references/etix-endpoints.md)
- [ContextMint Bridge releases](https://github.com/nullnet-app/contextmint-bridge/releases)
- [fetchproxy extension setup](https://github.com/chrischall/fetchproxy#extension)

## Skill Output:

**Output Type(s):** [Text, Shell commands, JSON]

**Output Format:** [Markdown guidance with shell commands and public event or venue data]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Public discovery only; no purchasing or logged-in account actions.]

## Skill Version(s):

1.1.7 (source: ClawHub release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.