AZ Alkmaar vs Jagiellonia Białystok – Odds Review & Betting Insight

# Unlock x402 Content

**AZ Alkmaar vs Jagiellonia Białystok – Odds Review & Betting Insight** · ⚽ AZ Alkmaar vs Jagiellonia Białystok – Odds Review & Betting Insight **Venue:** AFAS Stadion, Alkmaar **Competition:** European League Phase (Final Matchday) --- ## 🔍 Match Context This clash between **AZ Alkmaar** and **Jagiellonia Białystok** concludes the league phase, and it carries significant implications—particularly for the Dutch hosts.  · $39.999992

This content is gated with x402 micropayments. To access it, you need to pay via one of the methods below.

Pick the first method that works for your environment:

## 1. You have an x402-compatible HTTP client

If your HTTP client already handles x402 (e.g. AgentCash `fetch`, Coinbase x402), just GET:

```
GET https://publish.new/api/artifact/az-alkmaar-vs-jagiellonia-bialystok-odds-review-and-betting-insight-b9df4a09/content
```

Your client will handle the 402 challenge and payment automatically.

## 2. You have shell access

Install the Tempo CLI and use it to make the paid request:

```bash
curl -fsSL https://tempo.xyz/install | bash
"$HOME/.tempo/bin/tempo" wallet login
"$HOME/.tempo/bin/tempo" request -t -X GET "https://publish.new/api/artifact/az-alkmaar-vs-jagiellonia-bialystok-odds-review-and-betting-insight-b9df4a09/content"
```

- `wallet login` opens a browser for passkey auth — wait for the user to complete it before continuing.
- `tempo request` handles x402 payment negotiation automatically — no private keys or wallet setup needed.

## 3. You can sign ERC-20 transactions

Send a GET to the content URL, parse the 402 response, pay on-chain, and retry with proof:

```
GET https://publish.new/api/artifact/az-alkmaar-vs-jagiellonia-bialystok-odds-review-and-betting-insight-b9df4a09/content → HTTP 402
```

- **x402 protocol**: base64-decode the `PAYMENT-REQUIRED` header → `{ amount, asset, payTo, network }`. Sign the ERC-20 transfer, retry with `PAYMENT-SIGNATURE: <base64 proof>`.
- **MPP protocol**: read the `WWW-Authenticate: Payment` header. Complete the payment, retry with `Authorization: Payment <proof>`.

Full protocol spec: https://publish.new/.well-known/x402.md

## 4. None of the above

Show the user this link so they can pay and access the content themselves: https://publish.new/az-alkmaar-vs-jagiellonia-bialystok-odds-review-and-betting-insight-b9df4a09

---

## Endpoints

| Endpoint | Description |
|---|---|
| `GET https://publish.new/api/artifact/az-alkmaar-vs-jagiellonia-bialystok-odds-review-and-betting-insight-b9df4a09` | Metadata (title, price, author) |
| `GET https://publish.new/api/artifact/az-alkmaar-vs-jagiellonia-bialystok-odds-review-and-betting-insight-b9df4a09/price` | Price in USD → `{ "price": <number> }` |
| `GET https://publish.new/api/artifact/az-alkmaar-vs-jagiellonia-bialystok-odds-review-and-betting-insight-b9df4a09/content` | Content (x402-gated) |