Can I initiate upload process by submitting document metadata with the RAG Service API?

Yes. Use the POST /document-upload endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the RAG Service API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I initiate upload process by submitting document metadata through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'initiate upload process by submitting document metadata'. Jentic returns the matching RAG Service API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the RAG Service API have?

The RAG Service API exposes 6 endpoints covering document information summarised asynchronously, document information summarised synchronously, document ingestion initiation operations.

Can I limit what my agent is allowed to do with the RAG Service API?

Yes. Jentic One is self-hosted, so your own rules decide which of the RAG Service API operations your agent may call and which credentials it may use. Because this API carries the document reference and transaction id in the URL path (GET /document-upload/{documentReference}, GET /answer-user-query-async-status/{transactionId}), a rule can pin the agent to one document or query transaction and let it only check that item's status. You choose the operations it may call, so writes like POST /document-upload or POST /answer-user-query stay off unless you add them.