AIception Interactive

What authentication does AIception Interactive use?

HTTP Basic authentication using your AIception user account credentials. Through Jentic, the credentials live in the vault and are applied at request time, so the agent never holds the username and password directly.

How does the task pattern work in AIception?

Each capability has a POST endpoint that creates a task and returns a taskId, plus a GET /{capability}/{taskId} endpoint that returns the result. Poll the GET endpoint until the task is complete; processing time depends on the capability and image size.

How do I run object detection on an image through Jentic?

Search Jentic for 'detect the object in an image'. Load the POST /detect_object schema, supply the image_url, and execute. Jentic returns the taskId; load GET /detect_object/{taskId} to retrieve the label once processing completes.

Can I run multiple capabilities on the same image in parallel?

Yes. Each capability has its own POST endpoint and taskId namespace, so an agent can fire /face, /face_age, and /detect_object concurrently for one image and poll each task ID independently.

What are the rate limits for AIception Interactive?

The OpenAPI spec does not declare explicit per-second limits. Because tasks are async, throughput is bounded more by worker concurrency than request rate; poll task results with backoff rather than tight loops.

Can I limit what my agent is allowed to do with the AIception Interactive API?

Yes. Because Jentic One is self-hosted, you decide which AIception operations go into the agent's allowed set, and anything you leave out is not reachable. You can, for example, permit only the submit-and-fetch pair for face detection (POST /face and GET /face/{taskId}) while withholding adult content scoring or artistic image generation. Since result reads carry the task id in the URL path and image submissions take their input in the body, a rule can pin the agent to reading a specific task or restrict it to just the vision operations it needs.