Detect Code Language

Overview

Send a raw code snippet in a POST request. The service inspects the syntax to identify the language and returns its standard file extension and display name. Paid plans add detection confidence scores, language family, programming paradigms, and execution classification.

Live Test Detect Code Language Source →

Formula

One function covers the whole catalog: the first argument names the source, the rest are its inputs, and the "field" pair says which single value lands in the cell. Formulas covers the grammar that applies to all of them.

=VERVE("codedetector", A2, "field", "current")

A2 holds the code you are looking up. Drag the formula down and each row resolves on its own.

With literal values

Nothing has to come from a cell — typed values work the same way.

=VERVE("codedetector", "var test = '';", "field", "current")

Inputs

Required inputs are positional, in the order below. Everything else is passed as a "name", value pair after them — the same shape as SUMIFS. Premium inputs are accepted on every plan but only take effect on plans that include them.

Input	Type	Where it goes	Description
`code`Required	string	argument 2 (A2)	The code snippet you want to detect the programming language of length 0–50000

What lands in your sheet

The "field" pair is what makes the formula resolve to one cell. Its value is a dot-path from the table below, so swapping it is how you pull a different value — one formula per column.

Seeing everything at once

Drop the "field" pair and the formula returns the whole response instead: two columns, field name on the left and value on the right, spilling from the cell you typed in.

=VERVE("codedetector", A2)

Good for exploring, not for filling down

The second row's table would land on top of the first's, and every cell after the first reads #REF! (#SPILL! in Excel). Keep one per sheet, or name a field, and leave the cells below and to the right empty.

Response fields

Paths are relative to data. Each one is exactly what the "field" pair accepts, so swapping it is how you pull a different value into a cell. On a plan without a Premium field the cell reads #PREMIUM(field) rather than a value, so a locked field never looks like a real answer.

Use as "field"	Type	Example cell value	Description
`likelihood`Premium	number	`0.99`	Confidence score for code language detection (0.0 to 1.0)
`family`Premium	string	`PYTHON`	Programming language family or category classification
`current`	string	`python`	Detected programming language in lowercase format
`readable`	string	`Python Code`	Human-readable name of the detected programming language
`extension`	string	`.py`	Standard file extension for the detected language
`paradigm`Premium	string	`multi-paradigm`	Programming paradigm: object-oriented, functional, procedural, multi-paradigm
`isCompiled`Premium	boolean	`false`	Whether the language is compiled or interpreted

Filling a whole column

Both platforms make one batched call for a column rather than one request per cell, and both cost the same — 20 credits per row looked up. How you write it differs, because the two runtimes batch at different points.

Rows 2–100 in one call

=VERVE("codedetector", A2:A100, "field", "current")

In Google Sheets, give the arguments ranges and the answers spill down from the cell you typed in. Custom functions there run synchronously and in isolation, so dragged cells cannot be coalesced — the range form is how a column becomes one call. The "field" pair is required here: a per-row two-column table has nowhere to spill. Use a full column per input (A2:A100, not A2) — a single-cell reference is read as row 1 only and the rest of the column comes back blank.

In Excel, type the formula once and fill down — no range form and none needed, because its runtime is asynchronous and the add-in coalesces the calls a fill produces into a single batched request. Do not hand VERVE.CALL a range: Excel flattens it into positional arguments, so A2:A100 arrives as a hundred separate arguments and the cell reads #ERR rather than filling.

Either way, column A holds your code values and the answers land beside them, one row each, blank rows skipped.

When a cell doesn't fill

A failed lookup returns readable text starting with #ERR rather than a spreadsheet error, because Excel cannot show a custom message on a real error — you would get a bare #VALUE! with no reason. The trade-off is that IFERROR() will not catch it; test with LEFT(cell, 4) = "#ERR" instead. Error handling covers the rest.

Cell reads	What happened
`#ERR Not connected`	No API key saved. Open the side panel and connect your account.
`#ERR Replace <name> with a cell or value`	A preview formula was copied as-is. Swap the placeholder for a cell reference.
`#ERR No "x" in codedetector`	An option name this source does not take. The message lists the ones it does.
`#ERR No data point "…"`	The `"field"` path is not in the response. Check it against the table above.
`#PREMIUM(field)`	The field exists but your plan does not include it.
`#ERR Out of credits`	The cycle's credits are spent. Usage resets on your billing date.

Before the formula works

The add-in reads the API key you saved once in the side panel — the key never goes in the formula, so a shared sheet does not leak it and a collaborator without access simply sees the last calculated values.

Install the add-in for Google Sheets or Excel.
Open the side panel and sign in, or paste a key from your dashboard.
Type the formula above into any cell.

Use cases

Syntax Highlighting Setup: Developer forums inspect unformatted user pastes to pick the right code fence tag before rendering highlighted code blocks.
File Download Naming: When users export generated snippets from a web interface, editors apply the returned extension to name and save files accurately.
Documentation Snippet Tagging: Knowledge base platforms assign language labels to community-submitted examples without forcing authors to pick options from a manual dropdown.
Support Ticket Routing: To triage incoming developer issues containing raw scripts or stack traces, ticketing systems route requests based on the detected language.

Other ways to use Detect Code Language

Set up Detect Code Language on VerveSheets, or reach the same source a different way. Your VerveSheets account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →