LayerX

LayerX Inc. (株式会社LayerX) is a Tokyo-based enterprise software company founded 1 August 2018, operating as a compound startup across four business lines: Bakuraku (バクラク), an AI back-office suite covering expense reimbursement, invoice receipt and issuance, workflow and approvals, electronic bookkeeping, attendance, payroll and a corporate card; Ai Workforce, an enterprise LLM document-processing platform; a Fintech business run through the Mitsui-X / Mitsui & Co. Digital Asset Management joint venture; and a Security business added through the April 2026 acquisition of AgenticSec Inc. Its developer surface is the Bakuraku API — a REST API at api.bakuraku.layerx.jp built on an internal unified GraphQL gateway and tsoa, exposing application/approval retrieval and creation, attachment download, and tenant user, group and position directories. API access is granted by application to existing Bakuraku customers, who are issued a scoped API key from the Bakuraku admin console; the API reference at /rest/docs/ is HTTP Basic protected and no OpenAPI definition is published publicly.

LayerX publishes 1 API on the APIs.io network. Tagged areas include Company, Japan, Back Office, Expense Management, and Invoicing.

LayerX’s developer surface includes documentation, API reference, support, engineering blog, pricing, signup flow, authentication, and 20 more developer resources.

41.8/100 developing ▬ flat Agent 14/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
1 APIs
CompanyJapanBack OfficeExpense ManagementInvoicingAccounts PayableWorkflowApprovalsAccountingPayrollAttendanceCorporate CardsArtificial IntelligenceAI AgentsDocument ProcessingSaaSEnterprise SoftwareFintech

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 41.8/100 · developing
Contract Quality 0.0 / 21
Developer Ergonomics 7.7 / 17
Access Clarity 10.3 / 17
Operational Transparency 5.2 / 11
Contract Governance 1.9 / 10
Discoverability 7.4 / 9
Regulatory Posture 8.4 / 15
Agent readiness — 14/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/layerx: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Bakuraku API

REST API for the Bakuraku (バクラク) back-office suite. Publicly documented capabilities are retrieval and list-search of applications/requests (申請), download of attached files, cre...

Pricing Plans 1

Published pricing tiers and plan structures.

Layerx Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Layerx Rate Limits

0 limits

RATE LIMITS

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Layerx Authentication

1 scheme

SECURITY

Layerx Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Layerx Trust Center

ISO/IEC 27001 (ISMS), SOC 1 Type 2, JIIMA 電帳法スキャナ保存ソフト法的要件認証, JIIMA 電帳法電子取引ソフト法的要件認証

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 6

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: layerx
name: LayerX
description: 'LayerX Inc. (株式会社LayerX) is a Tokyo-based enterprise software company founded 1 August 2018, operating as a
  compound startup across four business lines: Bakuraku (バクラク), an AI back-office suite covering expense reimbursement, invoice
  receipt and issuance, workflow and approvals, electronic bookkeeping, attendance, payroll and a corporate card; Ai Workforce,
  an enterprise LLM document-processing platform; a Fintech business run through the Mitsui-X / Mitsui & Co. Digital Asset
  Management joint venture; and a Security business added through the April 2026 acquisition of AgenticSec Inc. Its developer
  surface is the Bakuraku API — a REST API at api.bakuraku.layerx.jp built on an internal unified GraphQL gateway and tsoa,
  exposing application/approval retrieval and creation, attachment download, and tenant user, group and position directories.
  API access is granted by application to existing Bakuraku customers, who are issued a scoped API key from the Bakuraku admin
  console; the API reference at /rest/docs/ is HTTP Basic protected and no OpenAPI definition is published publicly.'
image: https://layerx.co.jp/wp-content/uploads/2023/10/cropped-Icon_Square-300x300.png
url: https://raw.githubusercontent.com/api-evangelist/layerx/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-2026-08-23
specificationVersion: '0.20'
created: '2026-08-23'
modified: '2026-08-23'
tags:
- Company
- Japan
- Back Office
- Expense Management
- Invoicing
- Accounts Payable
- Workflow
- Approvals
- Accounting
- Payroll
- Attendance
- Corporate Cards
- Artificial Intelligence
- AI Agents
- Document Processing
- SaaS
- Enterprise Software
- Fintech
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Bakuraku API
  description: 'REST API for the Bakuraku (バクラク) back-office suite. Publicly documented capabilities are retrieval and list-search
    of applications/requests (申請), download of attached files, creation of applications for the purchase-request, payment-request
    and general-purpose application types, and read access to the tenant user, group and position directory. Bakuraku 請求書発行
    additionally exposes document upload (CSV/PDF) and recipient-master create/update. Authentication is a scoped API key
    issued from the Bakuraku admin console (API管理). Access requires an existing Bakuraku contract plus a separate API application;
    the reference at https://api.bakuraku.layerx.jp/rest/docs/ answers HTTP 401 with WWW-Authenticate: Basic to anonymous
    callers and no OpenAPI is published.'
  humanURL: https://bakuraku.jp/workflow/function/api/
  baseURL: https://api.bakuraku.layerx.jp/rest
  tags:
  - Expense Management
  - Invoicing
  - Workflow
  - Approvals
  - Back Office
  properties:
  - type: Documentation
    url: https://bakuraku.jp/workflow/function/api/
  - type: APIReference
    url: https://api.bakuraku.layerx.jp/rest/docs/
  - type: TermsOfService
    url: https://bakuraku.jp/terms/api-terms/
  - type: Authentication
    url: authentication/layerx-authentication.yml
  - type: Conventions
    url: conventions/layerx-conventions.yml
  - type: ErrorCatalog
    url: errors/layerx-error-codes.yml
  - type: RateLimits
    url: rate-limits/layerx-rate-limits.yml
  - type: Lifecycle
    url: lifecycle/layerx-lifecycle.yml
common:
- type: Website
  url: https://layerx.co.jp/
- type: DeveloperPortal
  url: https://bakuraku.jp/workflow/function/api/
- type: Documentation
  url: https://bakuraku.jp/workflow/function/api/
- type: APIReference
  url: https://api.bakuraku.layerx.jp/rest/docs/
- type: Support
  url: https://bakuraku-login.layerx.jp/hc/ja
- type: Blog
  url: https://tech.layerx.co.jp/
- type: GitHubOrganization
  url: https://github.com/LayerXcom
- type: Pricing
  url: https://bakuraku.jp/expense/price/
- type: SignUp
  url: https://id.layerx.jp/auth/sign_in
- type: TermsOfService
  url: https://bakuraku.jp/terms/api-terms/
- type: PrivacyPolicy
  url: https://layerx.co.jp/privacy/
- type: StatusPage
  url: https://bakuraku-status.jp/
- type: Security
  url: https://layerx.co.jp/security_policy/
- type: TrustCenter
  url: https://bakuraku.jp/security/
- type: Compliance
  url: conformance/layerx-conformance.yml
- type: Conformance
  url: conformance/layerx-conformance.yml
- type: VulnerabilityDisclosure
  url: security/layerx-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/layerx-domain-security.yml
- type: Authentication
  url: authentication/layerx-authentication.yml
- type: Conventions
  url: conventions/layerx-conventions.yml
- type: ErrorCatalog
  url: errors/layerx-error-codes.yml
- type: Lifecycle
  url: lifecycle/layerx-lifecycle.yml
- type: RateLimits
  url: rate-limits/layerx-rate-limits.yml
- type: Plans
  url: plans/layerx-plans-pricing.yml
- type: ChangeLog
  url: changelog/layerx-changelog.yml
- type: Packages
  url: packages/layerx-packages.yml
- type: LLMsTxt
  url: llms/layerx-llms.txt
x-enrichment:
  date: '2026-08-23'
  status: enriched
  artifacts_added: 17
  pass: local-v1
x-coverage:
  state: gated
  reason: customer-only-docs
  detail: 'The Bakuraku REST API is live and reachable at https://api.bakuraku.layerx.jp/rest — it answers anonymous calls
    with its own JSON error envelope and an x-layerx-request-id header — but its reference at /rest/docs/ sits behind HTTP
    Basic auth at the AWS load balancer (401, WWW-Authenticate: Basic), issued only to companies LayerX has approved as an
    "API契約者" on top of an existing Bakuraku subscription, and the API terms state the specification document is supplied separately
    to those customers, so no OpenAPI exists at any public URL.'
  evidence:
  - url: https://api.bakuraku.layerx.jp/rest/docs/
    status: 401
  - url: https://api.bakuraku.layerx.jp/rest/v1/tenant/users
    status: 400
  - url: https://api.bakuraku.layerx.jp/openapi.json
    status: 404
  - url: https://bakuraku.jp/terms/api-terms/
    status: 200
  checked: '2026-08-23'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/layerx"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/layerx/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/layerx/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.