Standardcompute Automation Integrations

Connect Standardcompute to Zapier, n8n, and Make.com using our OpenAI‑style API endpoints.

Base URL: https://api.stdcmpt.com Auth: Authorization: Bearer <API_KEY> Endpoints: /v1/completions · /v1/responses Unlimited (fair use) Multiple models

Overview

Standardcompute is built to be a plug‑and‑play AI API for automations. If your automation platform can send an HTTP request, it can use Standardcompute—no special SDKs required.

Best for

Customer support, summarization, content generation, classification, extraction, and “AI as a step” in workflows.

What customers get

One API key with unlimited fair‑use access and a selection of models.

Compatibility

OpenAI‑style request/response shapes for easy migration and tooling compatibility.

Authentication

All requests use a customer API key in the Authorization header:

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Tip: store the key in your automation platform’s “Secrets/Credentials” store (recommended) rather than directly in node/module configuration.

Core Endpoints

Endpoint	Use it for	Typical output
`POST /v1/completions`	Fast prompt → completion workflows. Great for “one‑shot” tasks.	Completion text under `choices[0].text` (OpenAI‑style)
`POST /v1/responses`	Richer responses and structured output workflows.	Convenient text field such as `output_text` (implementation dependent)

Example: /v1/completions

POST https://api.stdcmpt.com/v1/completions
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "model": "workflow",
  "prompt": "Summarize this message in 1 sentence:\n{{text}}",
  "max_tokens": 120,
  "temperature": 0.3
}

Example: /v1/responses

POST https://api.stdcmpt.com/v1/responses
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "model": "workflow",
  "input": "Extract key action items from this:\n{{meeting_notes}}"
}

Models & Subscription Tiers

Standardcompute currently offers three models, matched to subscription tier. Your API key determines which model(s) you can use. Switching models is as simple as changing the model value in your request—no new credentials required.

Subscription	Model value	Typical fit
Community	`community`	Everyday automations, drafts, summaries, lightweight reasoning.
Workflow	`workflow`	Reliable production workflows, routing, extraction, structured outputs.
Analyze	`analyze`	Deeper analysis, higher-accuracy tasks, more complex transformations.

Tip: If you’re migrating existing OpenAI-style workflows, keep everything the same and only update base URL, API key, and (optionally) the model field.

n8n Integration Best experience

n8n is the most flexible platform for custom APIs, and Standardcompute integrates cleanly in two ways:

True plug‑and‑play with n8n’s OpenAI tooling (when your n8n version supports a custom Base URL in OpenAI credentials).
Universal method using the n8n HTTP Request node (works in all versions).

True plug‑and‑play (OpenAI nodes): If your n8n OpenAI credentials screen includes a Base URL field, you can simply swap out OpenAI credentials and keep using the built‑in OpenAI nodes—no workflow refactor.

Option A — Use n8n OpenAI credentials (plug‑and‑play)

Go to Credentials in n8n.
Create or edit an OpenAI credential.
Set:
- API Key: YOUR_STANDARDCOMPUTE_API_KEY
- Base URL: https://api.stdcmpt.com/v1
Use the OpenAI/Chat/LLM nodes as usual.

Important: Some n8n versions/nodes do not expose a configurable OpenAI Base URL. If you don’t see a Base URL field (or your node ignores it), use Option B below (HTTP Request), which works everywhere.

Option B — HTTP Request node (works in all n8n versions)

Use HTTP Request and call Standardcompute directly:

Method: POST
URL: https://api.stdcmpt.com/v1/completions
Headers:
  Authorization: Bearer {{$env.STDCP_API_KEY}}
  Content-Type: application/json
Body (JSON):
{
  "model": "workflow",
  "prompt": "Rewrite this politely:\n{{$json.text}}",
  "max_tokens": 180,
  "temperature": 0.4
}

n8n use cases

Summarize incoming support tickets and route them by topic.
Classify leads from forms and auto-assign to teams.
Generate structured “next steps” from meeting notes.

Zapier Integration

Zapier is fantastic for fast no-code automations. For custom AI APIs, the most reliable approach is to use Webhooks by Zapier (Custom Request).

Action: Call Standardcompute using “Webhooks by Zapier”

Zapier’s most dependable method for custom AI APIs is the built-in Webhooks by Zapier app. Use the Custom Request action to send JSON to Standardcompute.

Step-by-step (Zapier UI)

Create a new Zap in Zapier.
Choose any Trigger app (for example: Gmail, Google Forms, Slack, Webhook Catch Hook).
Click the + button to add an Action.
Search for and select Webhooks by Zapier.
In Event, choose Custom Request.
Click Continue and configure:
- Method: POST
- URL: https://api.stdcmpt.com/v1/responses (or /v1/completions)
- Headers:
```
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
```
- Data / Body (JSON): paste a JSON body (example below)
Click Continue → Test step to verify you get a JSON response.

Example payload: /v1/responses

POST https://api.stdcmpt.com/v1/responses

{
  "model": "workflow",
  "input": "Summarize this in 3 bullet points:\n{{Text from previous step}}"
}

Example payload: /v1/completions

POST https://api.stdcmpt.com/v1/completions

{
  "model": "workflow",
  "prompt": "Rewrite this politely:\n{{Text from previous step}}",
  "max_tokens": 200,
  "temperature": 0.3
}

Zapier will expose fields from the JSON response so you can map them into later steps. For example, a completion may be accessible via choices__0__text depending on your Zapier UI mapping.

Zapier use cases

Google Forms → Standardcompute summary → Slack message
Gmail → classify intent → create CRM task
Spreadsheet row → generate description → publish draft

Make.com Integration

Make.com integrates cleanly through its HTTP module (“Make a request”) and custom webhooks. You can call Standardcompute in one module and map the response to subsequent steps.

HTTP Module: “Make a request” (recommended)

In Make.com, you can call Standardcompute using the HTTP app. This works for both /v1/completions and /v1/responses.

Step-by-step (Make.com UI)

Create a new Scenario.
Click the giant + button to add your first module.
Search for HTTP and select it.
Choose Make a request.
Configure the module:
- Method: POST
- URL: https://api.stdcmpt.com/v1/completions (or /v1/responses)
- Headers: add
```
Authorization: Bearer YOUR_API_KEY
```
  (If Make provides a dedicated JSON body content type field, you typically do not need to add Content-Type manually.)
- Body content type: choose application/json
- Body: select JSON string (raw) or Data structure and paste/map fields.
Click OK, then click Run once to test and inspect the output bundle.

Example JSON body: /v1/completions

{
  "model": "workflow",
  "prompt": "Turn this into a friendly customer reply:\n{{message}}",
  "max_tokens": 220,
  "temperature": 0.4
}

Example JSON body: /v1/responses

{
  "model": "workflow",
  "input": "Extract action items:\n{{meeting_notes}}"
}

Make.com use cases

Shopify order → generate confirmation message → email customer
Webhook event → extract entities → update Airtable
Content idea → generate post draft → schedule in social tool

Best Practices

Keep temperature low (0.2–0.5) for predictable automation steps.
Prefer structured prompts (e.g., “Return JSON with fields: …”) when you need consistent mapping.
Log request IDs (if included in responses) to simplify support and debugging.
Use /responses when you want richer or more structured output; use /completions for simpler text generation.

Troubleshooting

401 / Unauthorized

Verify the header is exactly: Authorization: Bearer YOUR_API_KEY
Confirm you are not sending the key as a query parameter.

400 / Bad Request

Ensure JSON is valid and Content-Type: application/json is set.
Confirm you are using the correct field names for the endpoint (prompt vs input).

n8n OpenAI nodes don’t allow Base URL

Use the n8n HTTP Request node method (always supported).

Implementation Notes & Sources

We keep this guide aligned with platform documentation and community-known behavior. For reference:

Zapier: “Send webhooks in Zaps” (Webhooks by Zapier setup, payload types, Custom Request): help.zapier.com
n8n OpenAI credentials overview: docs.n8n.io
n8n community discussion about custom Base URL in OpenAI credentials: community.n8n.io
n8n GitHub issue noting Base URL limitations in OpenAI node: github.com/n8n-io/n8n
Make.com HTTP module documentation (HTTP “Make a request”, JSON body options): apps.make.com
Make.com Webhooks documentation (Custom webhook setup and testing): help.make.com