# Page Not Found

The URL `g2p-bridge/development/design-specifications/persistent-objects` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [IN APIs from PBMS](https://docs.openg2p.org/products/g2p-bridge/development/design-specifications/persistent-objects.md)
- [create_disbursements](https://docs.openg2p.org/products/g2p-bridge/development/design-specifications/persistent-objects/disbursement.md)
- [Persistent Storage](https://docs.openg2p.org/operations/deployment/deployment-guide/persistent-storage.md)
- [cancel_disbursements](https://docs.openg2p.org/products/g2p-bridge/development/design-specifications/persistent-objects/cancel_disbursements.md)
- [Helper Tables](https://docs.openg2p.org/products/g2p-bridge/development/design-specifications/helper-tables.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.openg2p.org/products/g2p-bridge/development/design-specifications/persistent-objects.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://docs.openg2p.org/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.openg2p.org/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/products/g2p-bridge/development/design-specifications/persistent-objects.md`).

You may also use `Accept: text/markdown` header for content negotiation.
