Sandbox Linkcy Linkcy Api

Name: Linkcy Api
Brand: Linkcy Api
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingbearer102 EndpointsREST

For Agents

Programmatically update a rule from card, create a default card profile rule. Covers 102 operations with bearer authentication.

Install Jentic One Beta

Connect the Linkcy Api to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Linkcy 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Linkcy Api.

Update a rule from card

Create a default card profile rule

Verify phone verification code

Send phone verification code by sms

GET STARTED

Start building with Linkcy Api

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Linkcy Api for, with concrete tasks.

★ Finance and Accounting Operations

Use the Linkcy Api to perform finance operations programmatically. The API provides 102 endpoints covering core functionality including update a rule from card, create a default card profile rule, verify phone verification code.

Call PUT /api/partner/cards/{cardId}/rules to update a rule from card

Automated Card Management

Automate card operations by combining multiple Linkcy Api endpoints. Agents can create a default card profile rule and then verify phone verification code in a single workflow.

Call PUT /api/partner/card-profiles/{cardProfileId}/rules to create a default card profile rule, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Linkcy 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 'update a rule from card', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

102 endpoints — overview this is the partner api from [linkcy](https://linkcy.

METHOD

PATH

DESCRIPTION

PUT

/api/partner/cards/{cardId}/rules

Update a rule from card

PUT

/api/partner/card-profiles/{cardProfileId}/rules

Create a default card profile rule

POST

/api/partner/verifications/phone/verify

Verify phone verification code

POST

/api/partner/verifications/phone/send

Send phone verification code by sms

POST

/api/partner/verifications/email/send

Send an email verification link by email

POST

/api/partner/verifications/address

Verify the address of an end-user

POST

/api/partner/transactions

Create a transaction to a beneficiary

GET

/api/partner/transactions

List transactions

PUT

/api/partner/cards/{cardId}/rules

Update a rule from card

PUT

/api/partner/card-profiles/{cardProfileId}/rules

Create a default card profile rule

POST

/api/partner/verifications/phone/verify

Verify phone verification code

POST

/api/partner/verifications/phone/send

Send phone verification code by sms

POST

/api/partner/verifications/email/send

Send an email verification link by email

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Linkcy Api bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'update a rule from card') and Jentic returns the matching Linkcy Api operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Linkcy Api integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Linkcy Api through Jentic.

What authentication does the Linkcy Api use?

The Linkcy Api uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I update a rule from card with the Linkcy Api?

Yes. Use the PUT /api/partner/cards/{cardId}/rules endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Linkcy 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 update a rule from card through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'update a rule from card'. Jentic returns the matching Linkcy Api operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Linkcy Api have?

The Linkcy Api exposes 102 endpoints covering card, kyb, ledger operations.

Sandbox Linkcy Linkcy Api

Connect the Linkcy Api to your agent

Capabilities

Start building with Linkcy Api

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs