# Unif API agent development and sandbox guidance

UnifAPI does not publish a separate fake-data sandbox origin today. Public-data reads are real reads from supported public sources and may spend workspace credits. This page documents the safe development paths agents should use before running larger workflows.

- Last updated: 2026-06-02
- No-login tools: https://unifapi.com/tools.md
- Ask endpoint: https://unifapi.com/ask
- Auth guide: https://unifapi.com/auth.md
- Status guide: https://unifapi.com/status.md

## Safe test paths

- Use `/tools` and `/tools.md` for no-login demonstrations of the public-data layer before building a full Skill or HTTP integration.
- Use `/ask` for small NLWeb-style discovery questions; it can return JSON or Server-Sent Events without requiring a workspace key.
- Use the new-workspace trial grant for low-volume live API validation. Keep test queries small and record the operations used.
- Use MCP `list_operations` and `get_operation` before `call_api` so the agent can validate parameters without spending records on malformed requests.
- Use direct HTTP only after the operation path, method, query/body shape, and expected response are confirmed from OpenAPI or MCP inspection.

## What not to assume

- Do not assume a separate sandbox host, staging host, or fake-data key exists.
- Do not run bulk crawls or batch submissions as a test.
- Do not ask users to paste API keys into chat. Use MCP OAuth or environment/secret storage.
- Do not treat no-login demo output as a production SLA; use `status.md`, docs, and direct API validation for production readiness.

## Related resources

- [Tools](https://unifapi.com/tools.md)
- [Streaming support](https://unifapi.com/streaming.md)
- [Versioning and deprecation](https://unifapi.com/versioning.md)
- [Create API key](https://api.unifapi.com/sign-in)
- [Support contact](https://unifapi.com/contact.md)