Local services & SaaS
Procore
RFIs, submittals, punch lists, observations and daily logs on your Procore projects.
13 endpoints
GCPay publishes no public API and no MCP server (checked 16 Nov 2026). Cotlet runs a hosted GCPay MCP server with 17 tools that ChatGPT and Claude use in your own GCPay account. Approvals, submissions and anything that reaches a subcontractor wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by GCPay. GCPay is a trademark of its owner. If GCPay's own integrations cover what you need, use them first.
17 tools Read and write
GCPay publishes no public API: no developer documentation, API key page or API pricing was found on its site or in its Help Center. Its integrations are managed ERP connections that export approved items. No GCPay MCP server and no official ChatGPT or Claude connector was verified.
| What you need | GCPay ERP integration | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server | Copy and paste | Hosted MCP server |
| Review pay apps, waivers and compliance | Exports approved items | One sub at a time | 17 tools, writes after your OK |
| Works for subcontractors too | GC side only | Your login | Your login, once |
| Run from n8n or a script | No public API | Manual only | REST, same key |
Checked 16 Nov 2026. Sources: GCPay · GCPay integrations · GCPay pricing for general contractors · GCPay Help Center · Help: Add a vendor · Help: Create an application for payment · Help: Edit an AFP · Help: Submit an AFP · Help: Approve an AFP · Help: Reject an AFP · Help: AFP export status · Help: Delete an AFP · Help: Create a Schedule of Values · Help: Constrained Schedule of Values · Help: Edit a Schedule of Values · Help: Submit a Schedule of Values · Help: Approve a Schedule of Values · Help: Reject a Schedule of Values · Help: Delete a Schedule of Values · Help: Create a Change Order · Help: Approve a Change Order · Help: Reject a Change Order · Help: Upload compliance documents · Help: Verify a compliance item · Help: Add a waiver template to a project · Help: Upload a waiver · Help: Digitally sign a lien waiver · Help: Approve a waiver · Help: Unique or one-off waiver · Help: Bill for retention release · Help: Bulk release retention · Help: Add a subcontractor to a project · Help: Move stored material
Once, in a browser we host for you.
One address in its settings.
It reads each pay app, you approve.
Your agent works in your own signed-in Cloud Browser. Approvals, submissions and anything a subcontractor receives wait for your OK. Who can see your session
Sign in to GCPay in a Cloud Browser. Open gcpay.com/login.do in your Cotlet Cloud Browser and sign in with your own GCPay user.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
GCPay shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned GCPay on after connecting? Refresh the connector and the 17 GCPay tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: gcpay_read One tool per document type in the GCPay Help Center. Create, edit and submit share a tool; approving and rejecting have their own, so review rights stay separate.
Start here: what waits for review, and each project's schedules of values, pay applications and change orders.
Returns what the Submittals & Approvals and Lien Waivers widgets show your user: item, project, subcontractor, amount and status. Nothing is changed.
MCP callgcpay_read → list_submittals
REST endpointGET https://cotlet.dev/api/v1/gcpay/submittals
| Name | Type | Description |
|---|---|---|
| type string | string | `sov`, `afp`, `change_order`, `lien_waiver`, or empty for all. |
| project string | string | Limit to one project. |
{
"submittals": [
{
"type": "afp",
"project": "Riverside Medical Office",
"subcontractor": "Example Drywall Co",
"number": 4,
"amount": 16200,
"status": "Submitted"
},
{
"type": "change_order",
"project": "Riverside Medical Office",
"subcontractor": "Sample Electric",
"amount": 3400,
"status": "Submitted"
}
]
} Returns the tables of the project's Overview tab, or the tab you name, with each item's status: Not Submitted, Submitted, Approved or Rejected. Nothing is changed.
MCP callgcpay_read → view_project
REST endpointGET https://cotlet.dev/api/v1/gcpay/projects/view
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name, as view_project or list_submittals returns it. |
| tab string | string | `overview` (default), `compliance`, `lien_waivers` or `integration`. |
{
"project": "project"
} {
"project": "Riverside Medical Office",
"schedules_of_values": [
{
"subcontractor": "Example Drywall Co",
"value": 240000,
"status": "Approved"
}
],
"applications_for_payment": [
{
"subcontractor": "Example Drywall Co",
"number": 4,
"this_period": 18000,
"status": "Submitted"
}
]
} Only Admin or User Admin company permissions add subcontractors. A company not in GCPay gets an invite and must register before you can create its schedule of values. Moving the billing history of a running project is done by GCPay Support, not by this tool. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → manage_projects
REST endpointPOST https://cotlet.dev/api/v1/gcpay/projects/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create_project`, `add_company`, `invite_company`. |
| project string required | string | Project name. |
| company string | string | For `add_company`: name, tax ID, contact name or email to search GCPay by. |
| email string | string | For `invite_company`: the new company's contact email. |
{
"action": "action",
"project": "project"
} {
"project": "Riverside Medical Office",
"company": "Example Drywall Co",
"added": true
} Tier vendors are who tier lien waivers go to. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → add_tier_vendor
REST endpointPOST https://cotlet.dev/api/v1/gcpay/tier-vendors
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name, as view_project or list_submittals returns it. |
| subcontractor string | string | Subcontractor company on the project. |
| vendor object required | object | Vendor data, and for a disadvantaged business its certificate number and types (Small, Women-Owned, Minority-Owned, Veteran and others). |
{
"project": "project",
"vendor": "vendor"
} {
"project": "Riverside Medical Office",
"subcontractor": "Example Drywall Co",
"vendor": "Sample Supply",
"saved": true
} The contract lines every pay application bills against. Lines must add up to the contract value.
The subcontractor must already be on the project. Only a Not Submitted or Rejected SOV can be deleted; a submitted one has to be rejected first, and an approved one needs GCPay Support. `submit` stops on any requirement GCPay still shows in red. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → manage_schedule_of_values
REST endpointPOST https://cotlet.dev/api/v1/gcpay/schedule-of-values/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `create_constrained`, `edit_lines`, `submit`, `delete`. |
| project string required | string | Project name, as view_project or list_submittals returns it. |
| subcontractor string | string | Subcontractor company on the project. |
| value number | number | For `create_constrained`: contract value of the SOV. |
| retention_percent number | number | For `create_constrained`. |
| lines array | array | For `edit_lines`: description and value per line. The lines must add up to the contract value. |
| comment string | string | Comment for the email notification and the Audit Trail. |
{
"action": "action",
"project": "project"
} {
"project": "Riverside Medical Office",
"subcontractor": "Example Drywall Co",
"lines": 6,
"value": 240000,
"status": "Submitted"
} The comment goes to the subcontractor in GCPay's email and into the Audit Trail. An approved SOV is what pay applications bill against. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → review_schedule_of_values
REST endpointPOST https://cotlet.dev/api/v1/gcpay/schedule-of-values/review
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `approve`, `reject`. |
| project string required | string | Project name, as view_project or list_submittals returns it. |
| subcontractor string | string | Subcontractor company on the project. |
| comment string | string | Comment for the email notification and the Audit Trail. |
{
"action": "action",
"project": "project"
} {
"project": "Riverside Medical Office",
"subcontractor": "Example Drywall Co",
"status": "Approved"
} Billing this period, stored material, retainage and the release at the end, plus the ERP export flag.
Create needs an approved SOV and no open pay application. Submitting emails the reviewers. Only Admin or Editor permissions delete, and only before submission. The agent shows the lines, retainage and total before saving. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → manage_pay_applications
REST endpointPOST https://cotlet.dev/api/v1/gcpay/pay-applications/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `edit`, `submit`, `delete`. |
| project string required | string | Project name, as view_project or list_submittals returns it. |
| subcontractor string | string | Subcontractor company on the project. |
| number number | number | Pay application number, for `edit`, `submit` and `delete`. |
| period_to string | string | ISO date. GCPay defaults to the last day of the month. |
| lines array | array | Per SOV line: `this_period` dollars or `percent_complete`, and `material_stored`. Moving stored material means lowering `material_stored` and adding the same amount to `this_period`. |
| retainage object | object | type (`Standard` or `Variable`) and percent, or per-line percents for Variable. Only when the GC has unlocked retainage. |
| comment string | string | Comment for the email notification and the Audit Trail. |
{
"action": "create",
"project": "Riverside Medical Office",
"subcontractor": "Example Drywall Co",
"period_to": "2026-11-30",
"lines": [
{
"line": 1,
"description": "Metal stud framing",
"this_period": 12500,
"material_stored": 0
},
{
"line": 2,
"description": "Gypsum board, hang and finish",
"this_period": 5500,
"material_stored": 0
}
],
"retainage": {
"type": "Standard",
"percent": 10
}
} {
"project": "Riverside Medical Office",
"subcontractor": "Example Drywall Co",
"number": 4,
"this_period": 18000,
"retainage": 1800,
"net_due": 16200,
"status": "Not Submitted"
} Before it acts, the agent reads the documents, the Liabilities tab and the Audit Trail of the bill for you. With tiered approvers the status reads pending 1 of n until the last approval. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → review_pay_application
REST endpointPOST https://cotlet.dev/api/v1/gcpay/pay-application/review
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `approve`, `reject`. |
| project string required | string | Project name, as view_project or list_submittals returns it. |
| subcontractor string | string | Subcontractor company on the project. |
| number number required | number | Pay application number. |
| comment string | string | Required for `reject`: the reason, sent to the subcontractor and kept in the Audit Trail. |
{
"action": "action",
"project": "project",
"number": 1
} {
"project": "Riverside Medical Office",
"subcontractor": "Example Drywall Co",
"number": 4,
"status": "Approved"
} Bulk release creates the retainage pay applications for the subcontractors and needs at least one approved pay application on each contract. Released retainage is money owed, so the agent lists contracts and amounts first. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → release_retainage
REST endpointPOST https://cotlet.dev/api/v1/gcpay/retainage/release
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `bill_release`, `bulk_release`. |
| project string required | string | Project name, as view_project or list_submittals returns it. |
| subcontractors array | array | For `bulk_release`: the contracts to release. |
| waivers boolean | boolean | For `bulk_release`: true sends the project's default waivers, including finals; false suppresses them. |
{
"action": "action",
"project": "project"
} {
"project": "Riverside Medical Office",
"released": [
{
"subcontractor": "Example Drywall Co",
"retainage": 24000
}
],
"waivers": true
} This changes only the flag your ERP integration reads; it moves no money. Calling it again with the other value undoes it. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → set_export_status
REST endpointPUT https://cotlet.dev/api/v1/gcpay/export-status
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name, as view_project or list_submittals returns it. |
| numbers array required | array | Pay applications by subcontractor and number. |
| exported boolean required | boolean | True for EXPORTED, false for TO BE EXPORTED. |
{
"project": "project",
"numbers": "numbers",
"exported": true
} {
"project": "Riverside Medical Office",
"updated": 2,
"exported": true
} Added scope, priced line by line, submitted and approved like an SOV.
Creating needs Editor for CO permission on the project. Only Not Submitted or Rejected change orders can be edited or deleted; an approved one is reversed by GCPay Support. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → manage_change_orders
REST endpointPOST https://cotlet.dev/api/v1/gcpay/change-orders/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `edit`, `submit`, `delete`. |
| project string required | string | Project name, as view_project or list_submittals returns it. |
| subcontractor string | string | Subcontractor company on the project. |
| change_order string | string | Change order name, for every action but `create`. |
| lines array | array | For `create` and `edit`: description and total value per line. |
| comment string | string | Comment for the email notification and the Audit Trail. |
{
"action": "action",
"project": "project"
} {
"project": "Riverside Medical Office",
"subcontractor": "Sample Electric",
"change_order": "Added outlets, level two",
"total": 3400,
"status": "Not Submitted"
} Needs Reviewer for COs permission. An approved change order adds to what the subcontractor can bill. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → review_change_order
REST endpointPOST https://cotlet.dev/api/v1/gcpay/change-order/review
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `approve`, `reject`. |
| project string required | string | Project name, as view_project or list_submittals returns it. |
| subcontractor string | string | Subcontractor company on the project. |
| change_order string required | string | Change order name. |
| comment string | string | Required for `reject`. |
{
"action": "action",
"project": "project",
"change_order": "change order"
} {
"project": "Riverside Medical Office",
"change_order": "Added outlets, level two",
"status": "Approved"
} The documents a pay application waits on. Lien Officer and Compliance Officer permissions apply.
`sign` uses the signature already on file for your user; waivers that need a notary cannot be signed here. `add_unique` works only after GCPay Support enables unique waivers. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → manage_lien_waivers
REST endpointPOST https://cotlet.dev/api/v1/gcpay/lien-waivers/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `upload`, `sign`, `add_unique`. |
| project string | string | Leave empty to list waivers across projects. |
| waiver string | string | Waiver from `list`. |
| file_url string | string | For `upload`. |
{
"action": "action"
} {
"waivers": [
{
"project": "Riverside Medical Office",
"subcontractor": "Example Drywall Co",
"afp": 4,
"waiver": "Conditional progress waiver",
"status": "Outstanding"
}
]
} Needs Admin or Lien Officer permission. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → review_lien_waiver
REST endpointPOST https://cotlet.dev/api/v1/gcpay/lien-waiver/review
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `approve`, `reject`. |
| project string required | string | Project name, as view_project or list_submittals returns it. |
| waiver string required | string | Waiver from manage_lien_waivers `list`. |
{
"action": "action",
"project": "project",
"waiver": "waiver"
} {
"project": "Riverside Medical Office",
"waiver": "Conditional progress waiver",
"status": "Approved"
} Needs Admin or Lien Officer permission. Tier waivers also need Require Contractors to Provide Multi-Tier Contractor Information turned on in Project Settings. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → add_waiver_template
REST endpointPOST https://cotlet.dev/api/v1/gcpay/waiver-templates
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name, as view_project or list_submittals returns it. |
| template string required | string | A waiver template from Settings > Lien Waivers, standard or tier. |
| settings object | object | When to send, type of waiver and the general options. |
{
"project": "project",
"template": "template"
} {
"project": "Riverside Medical Office",
"template": "Conditional progress waiver",
"saved": true
} One document can cover several policies; the general contractor marks each one. The item stays red until the GC reviews it. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → upload_compliance_document
REST endpointPOST https://cotlet.dev/api/v1/gcpay/compliance-documents
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name, as view_project or list_submittals returns it. |
| requirement string required | string | The compliance item, as the Compliance tab names it. |
| file_url string required | string | A link the Cloud Browser can download the PDF from. |
{
"project": "project",
"requirement": "requirement",
"file_url": "https://example.com"
} {
"project": "Riverside Medical Office",
"requirement": "Certificate of insurance",
"last_upload": "2026-11-16",
"uploaded": true
} Needs the Compliance Officer or Admin company permission. `list` returns each requirement with its last upload date, so you can see what is missing before a pay application is approved. By default you confirm each call; you can switch that off for this tool.
MCP callgcpay_write → verify_compliance_items
REST endpointPOST https://cotlet.dev/api/v1/gcpay/compliance-items/verify
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `verify`, `reject`. |
| project string required | string | Project name, as view_project or list_submittals returns it. |
| subcontractor string | string | Subcontractor company on the project. |
| requirements array | array | For `verify` and `reject`. |
{
"action": "action",
"project": "project"
} {
"subcontractor": "Example Drywall Co",
"requirements": [
{
"name": "Certificate of insurance",
"last_upload": "2026-11-16",
"status": "Verified"
},
{
"name": "W-9",
"last_upload": null,
"status": "Missing"
}
]
} Your signed-in GCPay browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 17 GCPay tools. The session cookie stays in the Cloud Browser.
The projects your GCPay user is on, with that user's company and project permissions.
Users and permissions, company settings, your ERP integration setup and the signature you adopted.
You sign in again yourself, in the same Cloud Browser.
Disable GCPay for agents, reset the browser, or change your GCPay password.
Cotlet never sees or stores your password: you type it yourself, and the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
create, Not Submitted. submit emails the reviewers. | Action | How to put it right |
|---|---|
| Draft pay app, SOV or change order | Edit it, or delete it while Not Submitted |
| Submitted pay app or change order | Ask the reviewer to reject it, then edit |
| Export flag | set_export_status with the other value |
| Approved SOV or change order | Only GCPay Support reverses it |
All 15 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 2 read tools, the Dashboard and the project overview, run at once.
{
"name": "manage_pay_applications",
"arguments": {
"action": "create",
"project": "Riverside Medical Office",
"subcontractor": "Example Drywall Co",
"period_to": "2026-11-30",
"lines": [
{
"line": 1,
"description": "Metal stud framing",
"this_period": 12500,
"material_stored": 0
},
{
"line": 2,
"description": "Gypsum board, hang and finish",
"this_period": 5500,
"material_stored": 0
}
],
"retainage": {
"type": "Standard",
"percent": 10
}
}
} curl -X POST https://cotlet.dev/api/v1/gcpay/pay-applications/manage \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"create","project":"Riverside Medical Office","subcontractor":"Example Drywall Co","period_to":"2026-11-30","lines":[{"line":1,"description":"Metal stud framing","this_period":12500,"material_stored":0},{"line":2,"description":"Gypsum board, hang and finish","this_period":5500,"material_stored":0}],"retainage":{"type":"Standard","percent":10}}' {
"project": "Riverside Medical Office",
"subcontractor": "Example Drywall Co",
"number": 4,
"this_period": 18000,
"retainage": 1800,
"net_due": 16200,
"status": "Not Submitted"
} The example bills $12,500 of framing and $5,500 of board: $18,000 this period, less 10% retainage of $1,800, leaves $16,200 due. A cron job or n8n flow can make the same call over REST at /api/v1/gcpay with the same key and price, in JSON. Failed calls are free.
About $22 a monthfor a general contractor with four projects and about 40 subs billing monthly, 3,720 credits. Your GCPay plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning read of submittals and outstanding waivers | 1 × 22 | 220 |
| Compliance check per pay application | 1 × 40 | 400 |
| Pay application review and approval | 2 × 40 | 800 |
| Lien waiver review | 1 × 40 | 400 |
| Change orders, read and approve | 2 × 10 | 200 |
| Export flags for the ERP | 1 × 4 | 40 |
| Monday missing-compliance report, four projects | 4 × 4 | 160 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 222 calls | 3,720 |
The smallest pack, 5,000 credits for $29, covers this month. More projects and subs mean more calls.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| GCPay ERP integrations | Managed connections that export approved pay applications to your accounting system. | One direction, after approval; no review work and no AI agent. |
| GCPay email and fax with coversheets | Subs send waivers and compliance documents with a QR coversheet. | Documents only; someone still reviews and approves in GCPay. |
| By hand | Open each project and pay application in GCPay. | One sub at a time, only while someone is at the desk. |
Keep GCPay's ERP integration for your accounting export: it is the vendor's own route. Cotlet fits the review and paperwork around it, when you want ChatGPT, Claude or a script working in GCPay from your own login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the GCPay tools.
Sign up free at https://cotlet.dev/signup?app=gcpay, turn on GCPay under Integrations in the console and sign in at https://gcpay.com/login.do in your Cloud Browser. Then connect your AI agent and ask it what waits for review. The trial needs no card.
GCPay publishes no public API: no developer docs, API key page or API pricing was found on its site or help center (checked 16 Nov 2026). Its integrations are managed ERP connections that export approved pay applications. No GCPay MCP server and no official ChatGPT or Claude connector was verified. Cotlet does not need one: it works in your own signed-in GCPay account.
No. GCPay's managed integrations export approved pay applications to your ERP, and you keep them. set_export_status only changes the Exported flag on the Integration tab, the same switch GCPay documents.
Yes. A subcontractor user can edit and submit schedules of values, create and submit pay applications, upload compliance documents and sign lien waivers. Approvals need the general contractor's reviewer permissions.
The user whose reviews or billing the agent should prepare. A user without Reviewer permission on a project gives the agent no approve button there either.
Only in how it is called. Both carry the same 17 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with GCPay or Autodesk.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy