API access for humans and agents

One key. Precise control. Agent-ready.

Better ics API keys let applications and agents generate ICS files and manage selected backend settings. Every key is a bearer token with explicit scopes, observable usage, and limits you control.

Open /mcpExplore the access model
Bearer credential

Authorization

Bearer bics_live_••••••••••••

POST /v1/ics

scope: ics:generate

X-KEY-STATUS

active

X-USAGE

metered

Key governance

Credentials that behave like infrastructure, not passwords in a drawer.

Create and manage separate keys for each integration or agent. Restrict where they work, see exactly what they consume, and stop runaway automation before it becomes a surprise.

Optional expiration

Keep a key active indefinitely or set an expiry for temporary agents, campaigns, and integrations.

IP restrictions

Limit a key to approved source addresses when workloads run from known infrastructure.

Operation metering

Track usage per API key and per operation instead of relying on one opaque account total.

One limit. Three usage views.

Choose one limit window per API key: weekly, monthly, or lifetime. Usage is still tracked across all three windows and broken down by operation.

Budgets with boundaries

One limit. Three usage views.

Choose one limit window per API key: weekly, monthly, or lifetime. Usage is still tracked across all three windows and broken down by operation.

Weekly64%

Usage tracking

Monthly31%

Active limit

Lifetime12%

Usage tracking

Explicit authority

Give every key exactly enough power.

Scopes separate generation from backend management. Enable only the capabilities an integration needs, with independent read and write access where data can be managed.

01

Generate ICS files

ics:generate

When enabled, this execution scope provides the complete ICS generation capability. It is not split into read and write modes.

Full execution
02

Manage placeholder text blocks

placeholders:read · placeholders:write

Allow an agent to inspect reusable backend text blocks, change them, or both.

Read / write
03

Manage RSVP settings

rsvp:read · rsvp:write

Expose RSVP configuration as read-only context or permit controlled changes.

Read / write

Built-in discovery

/mcp

The shortest path from intent to a correct API call.

The MCP endpoint on this website gives compatible agents the tools and context they need to understand Better ics. Point an agent to /mcp and it can discover the product knowledge before touching the API.

Open /mcp

Knowledge base

Browse practical explanations and calendar infrastructure concepts.

Docs and guides

Find integration instructions, API behavior, and implementation guidance.

FAQs

Resolve common product, billing, security, and workflow questions.

An agent can learn before it acts.

Through /mcp, the agent discovers how Better ics works. Give it a bearer token with the required rights, let it inspect the effective scope, and it can generate ICS files or manage the web UI capabilities you explicitly enabled.

  1. 01

    Connect to /mcp

    The agent discovers Better ics tools and authoritative product context.

  2. 02

    Provide a limited key

    Supply a bearer token with only the scopes, network access, expiry, and budgets required.

  3. 03

    Inspect permissions

    The agent reads its effective scopes and limits before choosing an operation.

  4. 04

    Do the work

    Generate ICS files or manage enabled placeholders and RSVP settings through the API.

Make the API understandable to the agent using it.

/mcp is the stable discovery point for agents, while scoped keys remain the boundary for every action. The agent learns the system, verifies its authority, and works within the limits you set.

Open /mcpBrowse the docs

Treat API keys as secrets. Give agents only the minimum scopes and limits required, and never expose a bearer token to an untrusted tool or prompt.