Maysee Jp Maysee API
63
AI ReadinessAI-Aware (B)63/100
Agent-ready OpenAPI document · curated by JenticCRMContact ManagementapiKey3 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Count, retrieve, and create business-card profiles in Maysee's Japanese contact-management service. Use to sync scanned cards into a CRM.
Use for: I need to count how many business cards are in Maysee, Retrieve all Maysee profiles as JSON, Create a new profile from a scanned business card, Sync Maysee contacts into HubSpot
Not supported: Does not handle OCR card scanning, email outreach, or deal management - use for Maysee profile listing, counting, and creation only.
Jentic publishes the only available OpenAPI specification for Maysee API, keeping it validated and agent-ready. Maysee is a Japanese business-card management service that digitises and stores scanned business-card data for sales and CRM workflows. The API has three endpoints - count profiles, retrieve profiles as JSON, and create new profiles - letting agents synchronise scanned cards into a downstream CRM, dedupe contacts, or build a queryable contact directory.
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.
1
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%2Fmaysee.jp%2Fmaysee" | sh2
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%2Fmaysee.jp%2Fmaysee" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Filter profiles by metadata when reading the JSON list
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
Jentic AI Readiness Score
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.
M
Maysee API
- AI-Aware (B)63/100
87
Foundational Compliance63
Developer Experience & Jentic Compatibility43
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
43
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
22%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Maysee API by hand means sending your key in the X-API-Key header, pointing at the maysee.jp host, and mapping the profile operations yourself. Through Jentic you install once, import the Maysee API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Maysee's profile creation input travels in the request body rather than a resource id in the URL path, so you limit the agent to the operations it needs, such as counting or listing profiles. It calls only the operations you allow, so creating a profile is not included unless you add it.
Credential isolation
Your Maysee API key is stored once, encrypted, by your own Jentic One instance and injected into the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Maysee profiles', and Jentic returns the matching Maysee operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the Maysee API?
Yes. Because you run Jentic One yourself, your own rules decide which Maysee operations the agent may call and which credentials it may use. You can allow read-only access to counting profiles with GET /api2/profiles/count and listing them with GET /api2/profiles/json while withholding profile creation via POST /api2/profiles/create. The agent calls only the operations you permit, so it cannot write new business-card profiles unless you explicitly grant that operation.
GET STARTED