# Meeting Fetch by ID

> Meeting Fetch by ID is a paid API for AI agents from agentic-endpoints-testnet.oliver-835.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Retrieves the full details of a single meeting transcript by its meeting_id, authenticated with a namespace token

## Facts

- Endpoint: GET https://agentic-endpoints-testnet.oliver-835.workers.dev/meetings/get
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/meeting-fetch-by-id-621d283d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ew6iF7fpQiTjsws0hJYRX

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 meeting-fetch-by-id-621d283d
```

Example prompt: Pull up the full meeting transcript for meeting ID mtg_abc123 from my namespace 'team-standups' — I'll need the namespace token to authenticate.

## When to prefer this

Use this endpoint when you know the specific meeting_id and need the full transcript and metadata for a single meeting. Prefer this over the list or search endpoints when you already have the identifier and want complete content rather than excerpts or summaries.

## Known failure modes

- Invalid or expired namespace_token returns an authorization error
- Unknown meeting_id returns a not-found error
- Mismatched namespace and meeting_id returns a not-found or access-denied error
- Missing required parameters (meeting_id or namespace_token) returns a validation error
- Payment failure or missing x402 credit token results in a 402 Payment Required response

## How this service works

Fetch one meeting in full, by meeting_id (requires the namespace_token)

## Output

Returns the full meeting record for the requested meeting_id, including the complete transcript text and associated metadata such as title, timestamp, and visibility settings. Private meetings return decrypted content only when the correct namespace_token is supplied.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "namespace": {
   "type": "string",
   "description": "Meeting memory isolation scope"
  },
  "meeting_id": {
   "type": "string",
   "description": "Returned by /meetings/import"
  },
  "namespace_token": {
   "type": "string",
   "description": "One-time token issued when the namespace was claimed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/meeting-fetch-by-id-621d283d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentic-endpoints-testnet.oliver-835.workers.dev](https://www.zero.xyz/host/agentic-endpoints-testnet.oliver-835.workers.dev/llms.txt)