Can I run transactions across multiple documents with this API?

Yes. Begin a transaction with documents:beginTransaction, perform reads, then send writes through documents:commit referencing the transaction id. Use documents:rollback to abort cleanly.

What are the rate limits for the Cloud Firestore API?

Firestore enforces per-database write limits (around 10,000 writes per second per database) and per-document write limits (1 per second sustained). Read throughput scales much higher. Quota errors return HTTP 429 and should be retried with backoff.

How do I query Firestore from an agent through Jentic?

Search Jentic for 'query firestore documents', load the schema for POST /v1/{database}/documents:runQuery, and execute it with a structuredQuery payload describing the from, where, and orderBy clauses.

Does Firestore support realtime updates over this REST API?

Yes, through the documents:listen endpoint, which streams document change events. For most clients the official SDKs are simpler, but the REST listen channel is available for custom integrations.

Is the Cloud Firestore API free?

Firestore has a free daily quota of reads, writes, deletes, and storage. Beyond that it bills per operation and per GB stored. Pricing details are in the Firestore documentation.

Can I limit what my agent is allowed to do with the Cloud Firestore API?

Yes. Because you run Jentic One yourself, your own rules decide which Firestore operations and which service-account credential the agent may use. Firestore carries the database and document resource in the URL path (for example /v1/{database}/documents:commit and /v1/{name}), so you can pin the agent to a single database where it may read and query documents while excluding write paths like documents:commit or a document PATCH unless you explicitly allow them. Nothing outside the operations you approve is callable.