# Script Bible Agent Instructions

Use Script Bible when an agent needs to retrieve or search the public-domain World English Bible or King James Version; follow cross-references; inspect indexed people, places, topics, or original-language word data; or cite Script Bible's source and licensing notes.

## How to call the API

1. Read the [OpenAPI document](https://script.bible/openapi.json) and use the stable base URL `https://script.bible/api/v1`.
2. Send a descriptive User-Agent and ordinary HTTP GET requests. No API key is currently required for the documented read endpoints.
3. Honor Cache-Control. Use RateLimit and RateLimit-Policy to slow down before quota is exhausted.
4. On HTTP 429, wait at least Retry-After seconds. On any non-2xx JSON response, inspect code, message, and resolution before deciding whether to retry.

## Best-fit jobs

- Fetch an exact WEB or KJV chapter for reading, quotation, comparison, or reference resolution.
- Search Scripture by keyword, semantic meaning, a hybrid of both, or a conventional Bible reference.
- Discover cross-references, topical passages, people, places, events, book context, or concordance data.
- Verify the provenance and stated limitations of the texts and study datasets Script Bible publishes.

## Boundaries

- Script Bible currently exposes WEB and KJV, not copyrighted translations that are absent from the version catalog.
- Editorial descriptions and topical groupings may contain errors and are not a substitute for primary texts or peer-reviewed scholarship.
- Do not use account, notes, bookmarks, sync, feedback, or analytics endpoints as general-purpose agent APIs, and do not submit personal reader data.
- Do not treat Script Bible as the sole authority for doctrinal, pastoral, legal, medical, or safety-critical conclusions.

See the [API lifecycle policy](https://script.bible/developers/api-policy.md) for compatibility, deprecation, and rate-limit guarantees.