How to Connect CloudSign (クラウドサイン) to an AI Agent
Auth setup
1. Admin login to CloudSign. 2. Settings > API連携. 3. Generate API Key and Client ID. 4. Use both in request headers.
Key facts
| Base URL | https://api.cloudsign.jp/v1/ |
|---|
| API version | v1 |
|---|
| Auth | API Key + Client ID. Generate at CloudSign admin > Settings > API. Include X-Api-Key and X-Client-Id headers in every request. |
|---|
| Request body | application/json |
|---|
| Pagination | page-based: 'page' and 'per_page' params. |
|---|
| Rate limit | 100 requests/minute. HTTP 429 on exceed. |
|---|
| Error format | JSON: {"error":{"code":"invalid_request","message":"..."}} |
|---|
Key endpoints
| Method | Path | Description |
|---|
POST | /documents | Create a new contract document |
GET | /documents | List all documents with status filter |
POST | /documents/{id}/participants | Add signers to a document |
POST | /documents/{id}/send | Send document for signing |
GET | /documents/{id}/files | Download signed PDF |
Quickstart
GET /v1/documents?status=waiting HTTP/1.1
Host: api.cloudsign.jp
X-Api-Key: {api_key}
X-Client-Id: {client_id}
Response: {"documents":[{"id":"doc_123","title":"業務委託契約書","status":"waiting"}]}
Agent pitfalls & tips
- Requires BOTH X-Api-Key AND X-Client-Id headers. Missing either returns 401.
- Document workflow: create → add participants → upload PDF → send → wait for signing.
- Sandbox environment available — use it for testing. Documents in sandbox are not legally binding.
- Signed documents are legally valid under Japanese electronic signature law (電子署名法).
- Bulk send: POST /documents/bulk_send for sending up to 50 contracts at once (new in March 2026).
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-04. Specs change — verify against the official docs before production use.
Frequently Asked Questions
What is CloudSign (クラウドサイン)'s AEO score?
▼
CloudSign (クラウドサイン) has an AEO score of 0.60 and is rated BBB (Basic agent connectivity available). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is CloudSign (クラウドサイン) AI-agent-ready?
▼
CloudSign (クラウドサイン) is currently connectable for AI agent use. API access is available but no dedicated MCP server has been published yet. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does CloudSign (クラウドサイン) compare to other Legal & Contracts services?
▼
In the Legal & Contracts category, CloudSign (クラウドサイン) is rated BBB. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how CloudSign (クラウドサイン) compares.
How can I integrate CloudSign (クラウドサイン) with an AI agent?
▼
The fastest way to integrate CloudSign (クラウドサイン) with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server — then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with CloudSign (クラウドサイン)?
▼
API Key + Client ID. Generate at CloudSign admin > Settings > API. Include X-Api-Key and X-Client-Id headers in every request. Setup: 1. Admin login to CloudSign. 2. Settings > API連携. 3. Generate API Key and Client ID. 4. Use both in request headers.
What are CloudSign (クラウドサイン)'s API rate limits?
▼
100 requests/minute. HTTP 429 on exceed.