1. Playground Interface
The Playground interface combines a service selection panel, a configuration workspace, and a real-time response console in a structured layout.2. Using the Playground Module
The Playground section allows clients to test approved services and analyze request–response behavior before integrating them into production systems.Service Selection Panel
The left-side panel displays all services available to the client. For each service, clients can:- Search services using the search bar
- View available service categories (e.g., Document OCR, AML Screening, Proof of Address)
- Select a service to load it into the configuration workspace
Workbench (Configuration Workspace)
The central workspace allows users to configure and execute the selected service. For each selected service, clients can view:- Service Name — Displays the active service (e.g., Document OCR)
- Pricing — Cost per API call
- Execute Button — Triggers service execution
Request Configuration
The configuration section allows users to define inputs required for service execution. Depending on the service (e.g., Age Estimation), inputs may include:- Face Photo Upload — Upload an image containing a human face
- Supports drag & drop or manual file selection
- Displays file preview, name, and size after upload
- Option to replace the uploaded file
- Age Threshold — Numeric input field
- Defines the minimum age condition for evaluation
- Used to compare estimated age against a specified threshold
Response Console
The right-side panel displays the output of executed services. The console includes:- Default state — Console Idle before execution
- JSON response output after execution
- Extracted data (for services like OCR)
- Error messages (if applicable)
- Execution feedback
3. Operational Use Cases
The Playground module is commonly used for:- Testing approved services before API integration
- Validating input requirements (e.g., images and parameters)
- Reviewing real-time service responses
- Debugging failed or incorrect requests
- Understanding service behavior prior to deployment