Skip to main content
POST
/
api
/
v0
/
mutate
Mutation Agent
curl --request POST \
  --url https://agents.graphy.dev/api/v0/mutate \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "config": {
    "type": "column",
    "data": {
      "columns": [
        {
          "key": "region",
          "label": "Region"
        },
        {
          "key": "sales",
          "label": "Sales"
        }
      ],
      "rows": [
        {
          "region": "North",
          "sales": 100
        },
        {
          "region": "South",
          "sales": 80
        },
        {
          "region": "North",
          "sales": 120
        }
      ]
    }
  },
  "userPrompt": "Total sales by region, sorted highest first",
  "metadata": {
    "callId": "req-mutate-1",
    "locale": "EN_US"
  }
}
'
{
  "message": "<string>"
}
Transform a chart’s dataset with natural language — filter, group, aggregate, derive, sort. Send a GraphConfig and a prompt, receive an updated GraphConfig via Server-Sent Events.

​
Response

The response is a Server-Sent Events stream. See SSE Format for parsing details. 
event: progress
data: {"message":"Mutating dataset..."}

event: complete
data: {"config":{...},"response":{"message":"Grouped sales by region","steps":["Grouped rows by region","Sorted by total sales descending"]}}
Final response data: 
interface MutateResponse {
  config: GraphConfig;
  response: {
    message: string;
    steps?: string[];
  };
}

​
HTTP Status Codes

StatusDescription
200Success (stream begins)
400Invalid request body
401Invalid or missing API key
429Rate limit exceeded
500Internal server error
Errors may also arrive as SSE events within a 200 response. See Error Codes.

Authorizations

​
Authorization
string
header
required

Your Graphy API key

Body

application/json
​
config
object
required

The graph configuration object used to render charts. See Graph Config Schema for the complete reference.

​
userPrompt
string
required

Natural language instruction describing the desired changes

Maximum string length: 10000
​
metadata
object

Optional tracking information for requests

Response

SSE stream with progress and completion events

SSE event name is "progress"

​
message
string