contract-p.fit
Contract.fit provides a backend/API for processing and managing contract-related documents, inboxes, projects, roles, users, and related tenant settings. Its API includes authentication, document upload/processing, reporting, and administrative resources.
Contract.fit exposes one authenticated HTTP API at `//cfportal.contract-p.fit/api`, documented by a Swagger/OpenAPI document and accepting Basic auth, bearer JWTs, or API keys.
- Contract.fit APIdiscovered
Use the account credentials provided for your Contract.fit tenant. The OpenAPI states you should have an account to bootstrap your tenant and create users/roles, and says to contact Contract.fit if you are missing credentials or permissions.
Sign in with your Contract.fit account by calling the API POST /auth on your tenant API to exchange your username/password for a JWT token. If you do not yet have an account, contact Contract.fit.
Create an API key in Contract.fit using the API key management capability exposed at GET/POST /auth/api-key. The OpenAPI describes API keys as randomly generated strings bound to roles and says they can be revoked at any time. You need an existing authenticated account with permission to manage API keys; if you lack access, contact Contract.fit.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing