Install Jentic One Beta

Connect the Teampass API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Teampass 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%2Fteampass.net%2Fteampass" | sh

Step 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%2Fteampass.net%2Fteampass" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Teampass API.

Authenticate and get API key

List all items accessible to user

Get item by ID

Create a new item

Update an item

GET STARTED

Start building with Teampass API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Teampass API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Teampass API to perform identity auth operations programmatically. The API provides 16 endpoints covering core functionality including authenticate and get API key, list all items accessible to user, get item by id.

Call POST /api/index.php/auth to authenticate and get API key

Automated Items Management

Automate items operations by combining multiple Teampass API endpoints. Agents can list all items accessible to user and then get item by id in a single workflow.

Call GET /api/index.php/items to list all items accessible to user, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Teampass 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.

Search Jentic for 'authenticate and get API key', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

16 endpoints — teampass is a collaborative passwords manager.

METHOD

PATH

DESCRIPTION

POST

/api/index.php/auth

Authenticate and get API key

GET

/api/index.php/items

List all items accessible to user

GET

/api/index.php/items/{itemId}

Get item by ID

POST

/api/index.php/item

Create a new item

PUT

/api/index.php/item/{itemId}

Update an item

DELETE

/api/index.php/item/{itemId}

Delete an item

GET

/api/index.php/items/folder/{folderId}

List items in a folder

GET

/api/index.php/folders

List all folders

POST

/api/index.php/auth

Authenticate and get API key

GET

/api/index.php/items

List all items accessible to user

GET

/api/index.php/items/{itemId}

Get item by ID

POST

/api/index.php/item

Create a new item

PUT

/api/index.php/item/{itemId}

Update an item

DELETE

/api/index.php/item/{itemId}

Delete an item

GET

/api/index.php/items/folder/{folderId}

List items in a folder

GET

/api/index.php/folders

List all folders

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Teampass API by hand means calling its auth endpoint for an API key, pointing every request at your own self-hosted host, and writing the folder and item paging and retry glue yourself. Through Jentic you install once, import the Teampass API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The Teampass API puts the item id in the URL path (/api/index.php/item/{itemId}), so a rule can pin your agent to one item: it can read and update that item and nothing else. You choose the operations it may call, so destructive ones like deleting an item are not included unless you add them.

Credential isolation

Your Teampass 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.

Intent-based discovery

Agents search Jentic by intent such as 'read a stored item' or 'list folders', and Jentic returns the matching Teampass API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Teampass API through Jentic.

What authentication does the Teampass API use?

The Teampass API uses an API key passed in the `APIKEY` 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 authenticate and get API key with the Teampass API?

Yes. Use the POST /api/index.php/auth endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Teampass 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 authenticate and get API key through Jentic?

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

How many endpoints does the Teampass API have?

The Teampass API exposes 16 endpoints covering items, folders, users operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Teampass API operations and credentials the agent may use. Since the item id sits in the URL path (/api/index.php/item/{itemId}), a rule can pin the agent to a single item so it only reads and updates that one item and nothing else. You choose the operations it may call, so a destructive operation like deleting an item stays off limits unless you explicitly add it.

Teampass API

Name: Teampass API
Brand: Teampass API
Availability: InStock

Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationapiKey16 EndpointsREST

For Agents

Programmatically authenticate and get API key, list all items accessible to user. Covers 16 operations with apiKey authentication.

Use for: I need to authenticate and get API key, I want to all items accessible to user, Search for item by id, Find all a new item

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

Teampass is a collaborative passwords manager. The API enables CRUD operations on passwords/items, folders, and users with API key authentication. The API exposes 16 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Teampass API to your agent

Capabilities

Start building with Teampass API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Teampass API