developer.calendly.com agentic web readiness

A+ Manifest validity: 71% (5/7 valid, 3 errors, 2 warnings) · Surface score 60 (coverage 40 + breadth 15 + conformance 5). 7 standards observed across 4 of 9 steps; 7 manifests present, 3 errors, 2 warnings. Checked 2026-10-25 23:10:30 UTC. This grades the agent-facing files published at developer.calendly.com, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/developer.calendly.com.svg) · JSON · Markdown · Re-check now

Coverage by step

Manifests

# Authenticating to Developer as an agent

This file is the agent-auth skill for developer.calendly.com. It is linked from the authorization server's metadata (`agent_auth.skill`).

## Discovery
1. Call the API. A `401` carries `WWW-Authenticate: Bearer resource_metadata="https://developer.calendly.com/.well-known/oauth-protected-resource"`.
2. Read `/.well-known/oauth-protected-resource` (RFC 9728) for `resource` and `authorization_servers`.
3. Read the authorization server's `/.well-known/oauth-authorization-server` (RFC 8414); the `agent_auth` block lists the endpoints below.

## Methods we accept
- `identity_assertion`: you hold a session for a user and can mint an ID-JAG with `aud` = our `resource`. Preferred.
- `service_auth`: you only know the user's email. A claim ceremony (6-digit code) is required.
- `anonymous`: no user. Immediate limited scopes; the user can claim later.

## Register
POST `agent_auth.identity_endpoint` with `{"type": "<method>", ...}`; exchange the returned `identity_assertion` at the token endpoint for an access token.

## Scopes
- `api.read`: read
- `api.write`: write (claimed registrations only)

## Rules
- Show the user our name and the scopes before asserting their identity.
- Keep `claim_token` in memory only.
- Revocation events arrive as Security Event Tokens at your registered events endpoint.

---
okf_version: "0.2"
title: "Developer Knowledge Bundle"
description: "Developer and what it offers to agents"
---

# Developer Knowledge Bundle

> Developer and what it offers to agents

- [Update Log](log.md)

## Concepts

- [Developer Overview](concepts/developer.md) — Developer and what it offers to agents

What an agent can call

• API description https://developer.calendly.com/openapi/calendly-api.yaml (application/yaml)
• API description https://developer.calendly.com/api-docs/calendly-api (text/html)
• API description https://developer.calendly.com/openapi/calendly-oauth.yaml (application/yaml)
• API description https://developer.calendly.com/api-docs/calendly-o-auth (text/html)
• llms.txt: Calendly | Developer Documentation, 106 links, llms-full.txt present
• OKF bundle (/okf/index.md): Page Not Found, 3 concept links
• robots.txt AI policy: allows GPTBot; unlisted crawlers partial

Standards observed

• llms.txt https://developer.calendly.com/llms.txt
• AGENTS.md https://developer.calendly.com/AGENTS.md
• Content Signals Policy https://developer.calendly.com/robots.txt
• api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://developer.calendly.com/.well-known/api-catalog
• AI Crawler User-Agent Tokens in robots.txt https://developer.calendly.com/robots.txt
• Agent Skills https://developer.calendly.com/.well-known/agent-skills/index.json
• Markdown for Agents https://developer.calendly.com/

Cheapest next steps

1. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "developer.calendly.com"}))
2. security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people
   Generate starter /.well-known/security.txt for developer.calendly.com

   Contact: mailto:security@developer.calendly.com
   Expires: 2027-09-20T23:10:30Z
   Canonical: https://developer.calendly.com/.well-known/security.txt
   Preferred-Languages: en
   Policy: https://developer.calendly.com/security-policy
   

3. MCP Server Cards (SEP-2127): if you run an MCP server, a SEP-2127 card at <mcp-url>/server-card lets clients configure themselves (conditional spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "mcp-server-cards", "domain": "developer.calendly.com"}))

Agent pre-flight & practical readiness

Preferred mode: openapi (fallback agent_skills). Read the published API description and call those operations. Scraping HTML skips the interface the site already gave you.

Fetch: GET https://developer.calendly.com/openapi/calendly-api.yaml GET the API description and call the documented operations.

Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0.

AI crawler posture: search_allowed_training_blocked · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 14/20, readability 28/30, capabilities 19/35, conformance 5/15, total 66/100, grade A.

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules