Each path below starts with a bounded, inspectable contract. Test an authorized input, confirm the output and then choose the smallest direct plan that supports the recurring work.
The paths are deliberately small. They use the published direct prices and preserve a visible route to a demo, documentation and a person when the work needs a review.
Start with an authorized Google Maps search. Add public domain context and caller-supplied review evidence only when the use case warrants it.
Begin with PDF or image extraction, then add schema-first text conversion only when the downstream workflow needs normalized JSON.
Convert a permitted URL into clean Markdown, inspect the output and token estimate, then integrate it into an existing knowledge workflow.
For a more complex workflow, describe the source, the output that your team needs and the recurring frequency. Foundry/API can then identify the smallest appropriate contract and the relevant operating limits before an assisted deployment is discussed.