Install Jentic One Beta

Connect the Swapkaart API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Swapkaart 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%2Fswapkaart.com%2Fswapkaart" | 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%2Fswapkaart.com%2Fswapkaart" | 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 Swapkaart API.

Authenticate user and exchange credentials for tokens

Exchange token for access and refresh tokens

Fetch all contacts for the authenticated user

Get authenticated user information

GET STARTED

Start building with Swapkaart API

Explore with Jentic One

View OpenAPI Document

Automated Authentication Management

Automate authentication operations by combining multiple Swapkaart API endpoints. Agents can authenticate user and exchange credentials for tokens and then exchange token for access and refresh tokens in a single workflow.

Call POST /zappier/auth to authenticate user and exchange credentials for tokens, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Swapkaart 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 bearer tokens manually.

Search Jentic for 'login redirect for oauth flow', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — swapkaart is a digital business card platform for sales driven companies.

METHOD

PATH

DESCRIPTION

GET

/zappier/login

POST

/zappier/auth

Authenticate user and exchange credentials for tokens

POST

/zappier/access

Exchange token for access and refresh tokens

GET

/zappier/contacts

Fetch all contacts for the authenticated user

GET

/me

Get authenticated user information

GET

/zappier/login

POST

/zappier/auth

Authenticate user and exchange credentials for tokens

POST

/zappier/access

Exchange token for access and refresh tokens

GET

/zappier/contacts

Fetch all contacts for the authenticated user

GET

/me

Get authenticated user information

Why Jentic?

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

Setup

Wiring the Swapkaart API by hand means running its Firebase-token OAuth flow, attaching the bearer token to every call, and targeting its europe-west1 Cloud Functions host yourself. Through Jentic you install once, import the Swapkaart API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Swapkaart API works through auth and contact endpoints that take their inputs in the request body or return the caller's own record, so limit the agent to the operations it needs, such as fetching contacts or reading the current profile. You decide which operations it may call, and the rest stay out of reach.

Credential isolation

Your Swapkaart API bearer token 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 'get my contacts' or 'read the current profile', and Jentic returns the matching Swapkaart API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Swapkaart API through Jentic.

What authentication does the Swapkaart API use?

The Swapkaart API uses a Bearer token in the Authorization 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 login redirect for oauth flow with the Swapkaart API?

Yes. Use the GET /zappier/login endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Swapkaart 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 redirect for oauth flow through Jentic?

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

How many endpoints does the Swapkaart API have?

The Swapkaart API exposes 5 endpoints covering authentication, contacts, users operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Swapkaart API operations and credentials the agent may use. You can restrict it to only the endpoints it needs, such as GET /zappier/contacts to fetch contacts or GET /me to read the current profile, while keeping the authentication endpoints like POST /zappier/auth and POST /zappier/access out of reach. The operations you do not grant stay unavailable to the agent.

Swapkaart API

Name: Swapkaart API
Brand: Swapkaart API
Availability: InStock

Official vendor OpenAPI document · agent-readyCRMContact Managementbearer5 EndpointsREST

For Agents

Programmatically login redirect for oauth flow, authenticate user and exchange credentials for tokens. Covers 5 operations with bearer authentication.

Use for: I need to login redirect for oauth flow, I want to authenticate user and exchange credentials for tokens, Search for exchange token for access and refresh tokens, Find all fetch all contacts for the authenticated user

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

Swapkaart is a digital business card platform for sales driven companies. This API provides access to authentication, contact management, and user information via Zapier integration endpoints. The API exposes 5 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Connect the Swapkaart API to your agent

Capabilities

Start building with Swapkaart API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Swapkaart API