# Halowerk Bridge Capital Flow Metrics

> Halowerk Bridge Capital Flow Metrics is a paid API for AI agents from markt.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-15).

Returns bridged capital metrics for a blockchain — including total bridged USD, canonical vs. external bridge inflows/outflows, and net capital movement into or out of the chain over a specified period.

## Facts

- Endpoint: POST https://markt.halowerk.com/bridge
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-bridge-capital-flow-metrics-1bf74df9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_H6L0Nm9-D83LrQIdMXvo2

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 halowerk-bridge-capital-flow-metrics-1bf74df9 -d '<json body>'
```

Example prompt: What's the current bridged capital on Arbitrum — break it down into canonical vs external bridge inflows, show me the net USD flow sign, and give me the inflow and outflow totals for the last 24 hours.

## When to prefer this

Choose this endpoint when you need to understand cross-chain capital dynamics — specifically how much USD is locked in bridges on a given chain, whether capital is net flowing in or out, and how canonical bridge flows differ from third-party bridge flows. Prefer this over generic TVL APIs when you need the inflow/outflow decomposition and the net_usd sign signal for directional capital movement analysis.

## Known failure modes

- Unsupported chain key returns an error or empty result
- Time window too broad may result in data gaps or timeout
- Missing required POST body fields returns a 400-level error
- Chain with no bridge activity returns zero values across all fields
- Rate limiting or payment failure due to x402 protocol issues

## How this service works

Measures how much bridged capital sits on a chain and how that changed. bridged_usd is the sum of canonical and external value: what came in over the canonical bridge of the chain plus what third party bridges brought, while natively issued value is reported apart because it never crossed a bridge. net_usd carries its sign meaning in a field of its own, positive always means capital moved INTO the queried chain. inflow_usd and outflow_usd are the summed positive and negative steps of the sampled

## Output

Returns a structured object with bridged_usd (sum of canonical and external bridged value), natively_issued_usd (assets that never crossed a bridge), net_usd (signed value — positive = capital moved into the queried chain), inflow_usd (sum of positive bridge steps), and outflow_usd (sum of negative bridge steps) over the sampled period.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "type": "string",
   "default": "base",
   "pattern": "^[a-z0-9_-]{2,32}$",
   "description": "Chain to measure, as L2BEAT id or slug, for example base, arbitrum, op-mainnet, linea, scroll, starknet. Layer 2 and layer 3 chains only."
  },
  "period": {
   "enum": [
    "24h",
    "7d"
   ],
   "type": "string",
   "default": "24h",
   "description": "Length of the observed window: 24h or 7d."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-bridge-capital-flow-metrics-1bf74df9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from markt.halowerk.com](https://www.zero.xyz/host/markt.halowerk.com/llms.txt)