Maysee Jp Maysee API

Name: Maysee API
Brand: Maysee API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey3 EndpointsREST

For Agents

Count, retrieve, and create business-card profiles in Maysee's Japanese contact-management service. Use to sync scanned cards into a CRM.

Install Jentic One Beta

Connect the Maysee API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Maysee 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 Maysee API.

Count business-card profiles in the Maysee account

Retrieve profile records as JSON for export to a CRM

Create new profile records from parsed business-card data

Page through large profile sets for batch synchronisation

GET STARTED

Start building with Maysee API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Maysee API for, with concrete tasks.

★ Maysee to CRM Sync

Pull all Maysee business-card profiles on a schedule and upsert them into a downstream CRM such as HubSpot or Salesforce. The /api2/profiles/json endpoint returns profile records that can be paged through, deduplicated, and mapped to CRM contact fields. Sales teams that scan cards at events use this to ensure no card sits unprocessed in Maysee while the CRM is the system of record.

Call GET /api2/profiles/json paginated 100 at a time, upsert each profile into HubSpot by matching email, and return a count of created and updated contacts.

Profile Volume Reporting

Track how many business-card profiles have been captured in Maysee over time as a leading indicator of field-sales activity. The /api2/profiles/count endpoint returns the current total cheaply, suitable for daily polling without paging through the full data set. Sales operations teams plot this against quotas and event schedules.

Call GET /api2/profiles/count and write the value to a daily metrics table with today's date.

Bulk Profile Creation from External Sources

Push contacts captured in another system — for example a conference registration list — into Maysee so the sales team can manage them alongside scanned cards. The /api2/profiles/create endpoint accepts profile records one at a time, with the agent looping over the source list and handling rate-limit responses. This is the inverse of the CRM-sync use case.

For each row in a CSV of conference registrants, call POST /api2/profiles/create with the parsed name, company, and email, and return a list of created profile ids.

AI Agent for Business-Card Triage

Build an agent that watches for new Maysee profiles, classifies them by industry from the company name, and routes high-priority leads to a Slack channel. The agent searches Jentic for 'list Maysee profiles', loads the JSON-listing schema, and executes calls with vault credentials. Sales teams use this to surface qualified leads from a scanning queue without daily manual review.

Retrieve Maysee profiles created in the last 24 hours, classify each by industry using the company field, and post any classified as 'fintech' or 'healthcare' to the #priority-leads Slack channel.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for maysee api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api2/profiles/count

Return the count of profiles

GET

/api2/profiles/json

Retrieve profiles as JSON

POST

/api2/profiles/create

Create a new profile

GET

/api2/profiles/count

Return the count of profiles

GET

/api2/profiles/json

Retrieve profiles as JSON

POST

/api2/profiles/create

Create a new profile

Why Jentic?

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

Credential isolation

Maysee API keys are stored encrypted in the Jentic vault (MAXsystem) and injected into the X-API-Key header at execution time. Agents receive scoped access only and the raw key never appears in their context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list Maysee profiles') and Jentic returns the matching Maysee operation with its input schema, so the agent can call the right endpoint without reading the maysee.jp PDF documentation.

Time to first call

Direct Maysee integration: 1-2 days for API-key setup, pagination handling, and CRM mapping. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Maysee API through Jentic.

Why is there no official OpenAPI spec for Maysee API?

Maysee does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Maysee API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Maysee API use?

Maysee uses an API key passed in the X-API-Key header. Through Jentic, the key is stored encrypted in the MAXsystem vault and attached to outbound requests at execution time, so the raw key never enters the agent's prompt or transcript.

Can I create new business-card profiles with the Maysee API?

Yes. POST /api2/profiles/create accepts a profile payload with the parsed business-card fields and returns the new profile record. This is typically used to push contacts captured in another system — such as a conference registration list — into Maysee.

What are the rate limits for the Maysee API?

Maysee does not publish a detailed rate-limit table; the API is positioned for moderate-volume CRM-sync workloads rather than high-throughput bulk operations. Expect to handle occasional 429 responses with exponential back-off when running large initial syncs.

How do I sync Maysee profiles into my CRM through Jentic?

Search Jentic for 'list Maysee profiles', load the schema for GET /api2/profiles/json, and execute paginated calls until the result set is exhausted. Map each profile to your CRM's contact shape and upsert. Jentic attaches the X-API-Key header automatically.

Does the Maysee API expose card-scanning OCR?

No. The API operates on already-parsed profile data; OCR happens inside the Maysee app before profiles are persisted. Agents working with raw card images should use a separate vision API to extract fields and then call POST /api2/profiles/create.