Fathom install auth

Skill jeremylongshore/claude-code-plugins-plus-skills/plugins/saas-packs/fathom-pack/skills/fathom-install-auth

'Configure Fathom AI meeting assistant API access with API key authentication.From its SKILL.md

Install

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill fathom-install-auth

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.7 KB, 567 tokens by cl100k_base, as published. Nobody here has run it

Fathom Install & Auth

Overview

Set up Fathom AI API access for retrieving meeting transcripts, summaries, and action items. The API at api.fathom.ai/external/v1 uses X-Api-Key header authentication with per-user API keys.

Prerequisites

Fathom account (free or Team plan)
API access enabled in Settings

Instructions

Step 1: Generate API Key

Log in to https://fathom.video
Navigate to Settings > Integrations > API Access
Click Generate API Key
Copy and store the key securely

export FATHOM_API_KEY="your-api-key-here"

# Verify the key works
curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
  https://api.fathom.ai/external/v1/meetings?limit=1 | jq .

Step 2: Configure Environment

# .env -- NEVER commit
FATHOM_API_KEY=your-api-key
FATHOM_BASE_URL=https://api.fathom.ai/external/v1

# .gitignore
.env
.env.local

Step 3: Test API Connectivity

# List recent meetings
curl -s -H "X-Api-Key: ${FATHOM_API_KEY}" \
  "https://api.fathom.ai/external/v1/meetings?limit=5" \
  | jq '.meetings[] | {id: .id, title: .title, date: .created_at}'

Step 4: OAuth Setup (For Public Apps)

# For building integrations others will use, register an OAuth app
# at developers.fathom.ai for marketplace listing eligibility

# OAuth apps cannot use include_transcript or include_summary
# in list requests -- use individual recording endpoints instead

Error Handling

Error	Cause	Solution
`401 Unauthorized`	Invalid API key	Regenerate in Settings > API Access
`403 Forbidden`	Key lacks access	API keys access your meetings + team shared
`429 Too Many Requests`	Rate limit (60/min)	Implement backoff
Empty meetings list	No recordings yet	Record a meeting first

Resources

Next Steps

Proceed to fathom-hello-world to retrieve your first meeting transcript.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.