Laurel

Laurel is an AI timekeeping and work-intelligence platform for professional services firms — law, accounting and advisory. Rather than asking timekeepers to record their own time, Laurel passively captures work activity across the applications people already work in, then uses machine learning to enrich each activity with the who, what, when, where and how needed to build a review-ready timesheet. Reviewed time is released into the firm's existing billing or practice-management system, and Laurel's Signal product layers operational and profitability analytics on top of the resulting time data. Laurel exposes three public APIs — Identity, Time and Ingestion — authenticated with OAuth 2.0 machine-to-machine client credentials, and documents them at developer.laurel.ai for firms and partners building connectors.

Laurel publishes 3 APIs on the APIs.io network: Time Service API, Identity Service API, and Ingestion Service API. Tagged areas include Company, Ai, Timekeeping, Time Tracking, and Legal.

Laurel’s developer surface includes documentation, API reference, getting-started guide, authentication, support, engineering blog, signup flow, and 21 more developer resources.

45.3/100 developing Agent 70/100 agent native Full breakdown ↓
scored 2026-07-20 · rubric v0.4
3 APIs 1 MCP Servers 0 Features
CompanyAiTimekeepingTime TrackingLegalLegal TechAccountingProfessional ServicesBillingPractice ManagementWork IntelligenceAnalytics

API Rating

API Evangelist API Evangelist Rating How this is scored →
scored 2026-07-20 · rubric v0.4
Composite quality — 45.3/100 · developing
Contract Quality 9.4 / 25
Developer Ergonomics 13.5 / 20
Commercial Clarity 7.9 / 20
Operational Transparency 4.4 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 70/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
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/laurel: 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

Laurel Time Service API

The Time Service is the core of the Laurel platform: it holds entries (the units of captured and enriched time), timers, and the reference data time is booked against — clients,...

Laurel Identity Service API

The Identity Service issues API access and models who belongs to a firm. It carries the OAuth 2.0 client-credentials token exchange every other Laurel API depends on, plus custo...

Laurel Ingestion Service API

The Ingestion Service is the write path a connector uses to keep Laurel in sync with a firm's practice-management or billing system. It takes batch imports of clients, code type...

MCP Servers

laurel-mcp.yml

MCP SERVER

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Access & Security 6

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: laurel
name: Laurel
description: Laurel is an AI timekeeping and work-intelligence platform for professional services firms — law, accounting
  and advisory. Rather than asking timekeepers to record their own time, Laurel passively captures work activity across the
  applications people already work in, then uses machine learning to enrich each activity with the who, what, when, where
  and how needed to build a review-ready timesheet. Reviewed time is released into the firm's existing billing or practice-management
  system, and Laurel's Signal product layers operational and profitability analytics on top of the resulting time data. Laurel
  exposes three public APIs — Identity, Time and Ingestion — authenticated with OAuth 2.0 machine-to-machine client credentials,
  and documents them at developer.laurel.ai for firms and partners building connectors.
image: https://cdn.prod.website-files.com/63643fff1bf707ba2678d088/63643fff1bf707cf9178d0f3_Touch%20Icon.jpg
url: https://raw.githubusercontent.com/api-evangelist/laurel/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- gv
- initialized-capital
- ivp
x-tier: enriched
x-tier-reason: three published OpenAPI documents harvested from developer.laurel.ai
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Ai
- Timekeeping
- Time Tracking
- Legal
- Legal Tech
- Accounting
- Professional Services
- Billing
- Practice Management
- Work Intelligence
- Analytics
apis:
- aid: laurel:time
  name: Laurel Time Service API
  description: 'The Time Service is the core of the Laurel platform: it holds entries (the units of captured and enriched
    time), timers, and the reference data time is booked against — clients, initiatives (matters/engagements), code types
    and billing codes. It also carries the access restrictions and validation rules that decide who may bill to a matter and
    which codes are valid on it, and it is the surface a firm reads from to release reviewed time into billing. 241 operations
    across v1, v2 and v3, served from a region-specific host issued per customer.'
  humanURL: https://developer.laurel.ai/services/time
  baseURL: https://api.laurel.ai/time/
  tags:
  - Time
  - Entries
  - Timers
  - Initiatives
  - Codes
  - Clients
  properties:
  - type: OpenAPI
    url: openapi/laurel-time-openapi-original.json
  - type: Overlay
    url: overlays/laurel-time-overlay.yaml
  - type: Documentation
    url: https://developer.laurel.ai/services/time
- aid: laurel:identity
  name: Laurel Identity Service API
  description: The Identity Service issues API access and models who belongs to a firm. It carries the OAuth 2.0 client-credentials
    token exchange every other Laurel API depends on, plus customers (firms), tenants, users (timekeepers and administrators),
    user identities, roles, permissions, user groups, delegates and SSO connections including SCIM provisioning. 95 operations
    across v1 and v2.
  humanURL: https://developer.laurel.ai/services/identity
  baseURL: https://identity.laurel.ai
  tags:
  - Identity
  - OAuth
  - Users
  - Customers
  - Roles
  - SCIM
  properties:
  - type: OpenAPI
    url: openapi/laurel-identity-openapi-original.json
  - type: Overlay
    url: overlays/laurel-identity-overlay.yaml
  - type: Documentation
    url: https://developer.laurel.ai/services/identity
  - type: Authentication
    url: https://developer.laurel.ai/guides/authentication
- aid: laurel:ingestion
  name: Laurel Ingestion Service API
  description: The Ingestion Service is the write path a connector uses to keep Laurel in sync with a firm's practice-management
    or billing system. It takes batch imports of clients, code types, codes and initiatives, binds access restrictions and
    permitted codes to each initiative, sets entry validation rules, manages delegates, and handles released and unreleased
    time entries flowing back from billing. Writes are largely asynchronous, returning 202 Accepted. 28 operations.
  humanURL: https://developer.laurel.ai/services/ingestion
  baseURL: https://api.laurel.ai/ingestion/
  tags:
  - Ingestion
  - Import
  - Batch
  - Entries
  - Connector
  properties:
  - type: OpenAPI
    url: openapi/laurel-ingestion-openapi-original.json
  - type: Overlay
    url: overlays/laurel-ingestion-overlay.yaml
  - type: Documentation
    url: https://developer.laurel.ai/services/ingestion
  - type: BuildingBlock
    url: https://developer.laurel.ai/guides/building-a-connector
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.laurel.ai
- type: DeveloperPortal
  url: https://developer.laurel.ai
- type: Documentation
  url: https://developer.laurel.ai
- type: APIReference
  url: https://developer.laurel.ai/guides/public-api-endpoints
- type: GettingStarted
  url: https://developer.laurel.ai/guides/authentication
- type: Authentication
  url: authentication/laurel-authentication.yml
- type: Support
  url: https://intercom.help/laurel/en/
- type: Blog
  url: https://www.laurel.ai/resources?category=Blog
- type: SignUp
  url: https://www.laurel.ai/get-a-demo
- type: Login
  url: https://app.laurel.ai
- type: PrivacyPolicy
  url: https://www.laurel.ai/privacy-policy
- type: StatusPage
  url: https://status.laurel.ai/
- type: Deprecation
  url: lifecycle/laurel-lifecycle.yml
- type: Lifecycle
  url: lifecycle/laurel-lifecycle.yml
- type: Security
  url: https://www.laurel.ai/responsible-disclosure-policy
- type: VulnerabilityDisclosure
  url: security/laurel-vulnerability-disclosure.yml
- type: TrustCenter
  url: security/laurel-trust-center.yml
- type: Compliance
  url: https://trust.laurel.ai/
- type: DomainSecurity
  url: security/laurel-domain-security.yml
- type: Conformance
  url: conformance/laurel-conformance.yml
- type: Conventions
  url: conventions/laurel-conventions.yml
- type: Idempotency
  url: conventions/laurel-conventions.yml
- type: DataModel
  url: data-model/laurel-data-model.yml
- type: MCPServer
  url: mcp/laurel-mcp.yml
- type: AgentSkill
  url: skills/_index.yml
- type: AgenticAccess
  url: agentic-access/laurel-agentic-access.yml
- type: LLMsTxt
  url: llms/laurel-llms.txt
- type: WellKnown
  url: well-known/laurel-well-known.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence