Contact

Volume pricing, archive depth, a coverage question, or something the documentation did not answer. This reaches a person.

What to include so the first reply is useful

For pricing questions, the two things that determine the answer are how far back you need to query and roughly how many requests a month you expect. Everything else is detail. If you are not sure about request volume yet, describe the workload instead — a scheduled monitoring job and an interactive assistant with the same number of users produce very different traffic, and we can estimate from the shape.

For coverage questions, naming the languages, regions or outlets you care about lets us answer with real numbers from the index rather than with a general reassurance. If the coverage is not there, we will say so.