For Agents
Programmatically login, password recover by email. Covers 367 operations with basic, bearer authentication.
Use for: I need to login, I want to password recover by email, Search for change password, Find all logout
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Sinao API for account management, apps administration and network exploration. The API exposes 367 endpoints secured with basic, bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sinao API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsinao.app%2Fsinao-api" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsinao.app%2Fsinao-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Sinao API.
Login
Password recover by email
Change password
Logout
Send 2FA code
GET STARTED
Refresh a token
Update current user
Patterns agents use Sinao API for, with concrete tasks.
★ Developer Tools Operations
Use the Sinao API to perform developer tools operations programmatically. The API provides 367 endpoints covering core functionality including login, password recover by email, change password.
Call POST /login to login
Automated Accountingfirm Management
Automate accountingfirm operations by combining multiple Sinao API endpoints. Agents can password recover by email and then change password in a single workflow.
Call POST /sendpassword to password recover by email, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Sinao API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic, bearer tokens manually.
Search Jentic for 'login', load the operation schema, and execute with Jentic-managed credentials
367 endpoints — sinao api for account management, apps administration and network exploration.
METHOD
PATH
DESCRIPTION
/login
Login
/sendpassword
Password recover by email
/changepassword
Change password
/logout
Logout
/login/send/2fa
Send 2FA code
/refresh
Refresh a token
/me
Update current user
/me
Get current user
/login
Login
/sendpassword
Password recover by email
/changepassword
Change password
/logout
Logout
/login/send/2fa
Send 2FA code
/refresh
Refresh a token
/me
Update current user
/me
Get current user
What agents get from Jentic-routed access to this vendor.
Setup
Wiring this Sinao API by hand means handling its mixed basic and bearer auth, choosing the api.sinao.app host over its dev and test variants, and carrying tokens across the login, refresh, and account calls yourself. Through Jentic you install once, import Sinao from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
This Sinao API identifies the caller by the authenticated session rather than a resource id in the URL path, so scope the agent by operations: limit it to the operations it needs, such as logging in or reading the current account with /me, and leave out changes like a password change unless you add them.
Credential isolation
Your Sinao credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'log in' or 'read the current user', and Jentic returns the matching Sinao operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Sinao API through Jentic.
What authentication does the Sinao API use?
The Sinao API uses basic, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I login with the Sinao API?
Yes. Use the POST /login endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Sinao 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 login through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'login'. Jentic returns the matching Sinao API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Sinao API have?
The Sinao API exposes 367 endpoints covering accountingfirm, apps, changepassword operations.
Can I limit what my agent is allowed to do with the Sinao API?
Yes. Because the Sinao API identifies the caller by the authenticated session rather than a resource id in the path, you scope the agent by the operations you allow. Since you self-host Jentic One, your own rules decide which Sinao operations and credentials the agent may use, so you can permit it to log in and read the current account with GET /me while leaving out changes like POST /changepassword. Grant only the operations the agent actually needs.