canonical: https://jentic.com/apis/sawolabs.com/sawolabs

# SAWO Labs API

SAWO Labs provided passwordless authentication as a service. The API enabled developers to integrate passwordless login (via email or phone OTP) into their applications. Note: SAWO Labs appears to be defunct as of 2026; the domain sawolabs.com no longer serves its original content. The API exposes 4 endpoints secured with apiKey authentication.

## For AI agents

Programmatically verify authentication token, get project details. Covers 4 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Verify authentication token
- Get project details
- Initiate passwordless login
- Query and filter SAWO Labs API records by parameters
- Monitor SAWO Labs API operational status and events

## Use cases

### Communications Operations

Use the SAWO Labs API to perform communications operations programmatically. The API provides 4 endpoints covering core functionality including verify authentication token, get project details, initiate passwordless login.

Example prompt: Call POST `/verify/token` to verify authentication token

### Automated Authentication Management

Automate authentication operations by combining multiple SAWO Labs API endpoints. Agents can get project details and then initiate passwordless login in a single workflow.

Example prompt: Call GET `/project/get` to get project details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SAWO Labs 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 apiKey tokens manually.

Example prompt: Search Jentic for 'verify authentication token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/verify/token` | Verify authentication token |
| GET | `/project/get` | Get project details |
| POST | `/user/login` | Initiate passwordless login |
| POST | `/user/verify-otp` | Verify OTP |

## Key resources

- **Authentication** — Passwordless authentication operations
- **Project** — Project management operations

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/sawolabs.com/sawolabs/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the SAWO Labs API by hand means passing your key in the x-sawo-api-key header and sequencing the login, OTP verify, and token verify calls yourself. Through Jentic you install once, import the SAWO Labs API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The SAWO Labs API takes its login and token details in the request body rather than the URL path, so you limit the agent to the operations it needs, such as verifying an OTP or a token, and you leave out other operations like reading project settings unless you add them. Every operation the agent runs is one you chose.
- **Credential handling:** Your SAWO Labs API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'verify an authentication token' or 'verify an OTP', and Jentic returns the matching SAWO Labs API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the SAWO Labs API use?

The SAWO Labs API uses an API key passed in the `x-sawo-api-key` header. 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 verify authentication token with the SAWO Labs API?

Yes. Use the POST `/verify/token` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SAWO Labs 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 verify authentication token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'verify authentication token'. Jentic returns the matching SAWO Labs API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SAWO Labs API have?

The SAWO Labs API exposes 4 endpoints covering authentication, project operations.

### Can I limit what my agent is allowed to do with the SAWO Labs API?

Yes. Because you run Jentic One yourself, your own rules decide which SAWO Labs operations and credentials the agent may use, so you can grant just verifying an OTP or a token and leave out reading project settings or initiating a login. The SAWO Labs API passes its login and token details in the request body rather than the URL path, so you scope access at the operation level and the agent only calls the endpoints you added. Every operation it runs is one you chose.