# Delete Meeting from Namespace

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

Deletes a specific meeting record and removes it from the full-text search index within an isolated namespace, requiring a namespace token for authorization.

## Facts

- Endpoint: GET https://agentic-endpoints-testnet.oliver-835.workers.dev/meetings/delete
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delete-meeting-from-namespace-0177de9c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__DmKpUv4Yor1reHrAdHMc

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 delete-meeting-from-namespace-0177de9c
```

Example prompt: Delete the meeting with ID mtg_abc123 from my namespace 'team-standups' — I have my namespace token ready, and I want it completely removed from the search index too.

## When to prefer this

Use this endpoint when you need to permanently remove a specific meeting transcript and its search index entry from a namespace you own, identified by the meeting_id returned at import time. Prefer this over listing-only or search operations when the goal is destruction rather than retrieval. Requires possession of the namespace_token issued at namespace claim time.

## Known failure modes

- Invalid or expired namespace_token returns an authorization error
- Unknown meeting_id returns a not-found error
- Incorrect namespace causes a mismatch or not-found error
- Attempting to delete an already-deleted meeting may return a 404 or idempotent success
- Missing required parameters returns a validation error
- Network or worker timeout returns a 5xx error

## How this service works

Delete a meeting and remove it from the search index (requires the namespace_token)

## Output

A confirmation that the meeting has been deleted and de-indexed from the namespace. After a successful call, the meeting_id is no longer retrievable via search or listing endpoints within that namespace.

## 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/delete-meeting-from-namespace-0177de9c/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)