Skip to content
Reference

GET /api/v1/port

The headline: net worth, its parts, the figure per wallet and what is not counted.

The key is read from PORT_API_KEY, so the command never prints it.

curl -s https://getport.app/api/v1/port -H "Authorization: Bearer $PORT_API_KEY"

A 200 with the envelope every endpoint answers, and this endpoint's answer in data. Amounts and USD figures are strings.

What data looks like, with sample values: the shape is the schema's, checked when these pages are built, and the figures are made up, not anyone's port.

{
"netWorthUsd": "48210.73",
"parts": {
"spotUsd": "39120.10",
"venueUsd": "6410.22",
"perpsUsd": "2680.41"
},
"byWallet": [
{
"address": "0x8f3c0e7b2a91d4c6f5e3b2a1908d7c6b5a4fc21a",
"family": "evm",
"label": "Vault",
"totalUsd": "31402.88",
"tokensUsd": "27011.40",
"defiUsd": "4391.48"
}
],
"hidden": {
"spam": 12,
"dust": 31,
"airdrop": 4,
"thin": 2,
"unpriced": 3,
"stale": 0
},
"chains": [
{
"address": "0x8f3c0e7b2a91d4c6f5e3b2a1908d7c6b5a4fc21a",
"chainId": "ethereum",
"name": "Ethereum",
"refreshedAt": "2026-10-06T05:41:52.000Z",
"refreshing": false,
"incomplete": null
}
]
}
Field of dataTypeAlways present
netWorthUsdstringyes
partsobjectyes
byWalletarray of objectyes
hiddenobjectyes
chainsarray of objectyes
The whole schema of data

As the OpenAPI document at https://getport.app/api/v1/openapi.json states it. Objects are left open, because a response only ever gains fields.

{
"type": "object",
"properties": {
"netWorthUsd": {
"type": "string"
},
"parts": {
"type": "object",
"properties": {
"spotUsd": {
"type": "string"
},
"venueUsd": {
"type": "string"
},
"perpsUsd": {
"type": "string"
}
},
"required": [
"spotUsd",
"venueUsd",
"perpsUsd"
]
},
"byWallet": {
"type": "array",
"items": {
"type": "object",
"properties": {
"address": {
"type": "string"
},
"family": {
"type": "string",
"enum": [
"evm",
"svm",
"cex",
"btc",
"move",
"tvm",
"near"
]
},
"label": {
"type": [
"string",
"null"
]
},
"totalUsd": {
"type": "string"
},
"tokensUsd": {
"type": "string"
},
"defiUsd": {
"type": "string"
}
},
"required": [
"address",
"family",
"label",
"totalUsd",
"tokensUsd",
"defiUsd"
]
}
},
"hidden": {
"type": "object",
"properties": {
"spam": {
"type": "integer",
"minimum": -9007199254740991,
"maximum": 9007199254740991
},
"dust": {
"type": "integer",
"minimum": -9007199254740991,
"maximum": 9007199254740991
},
"airdrop": {
"type": "integer",
"minimum": -9007199254740991,
"maximum": 9007199254740991
},
"thin": {
"type": "integer",
"minimum": -9007199254740991,
"maximum": 9007199254740991
},
"unpriced": {
"type": "integer",
"minimum": -9007199254740991,
"maximum": 9007199254740991
},
"stale": {
"type": "integer",
"minimum": -9007199254740991,
"maximum": 9007199254740991
}
},
"required": [
"spam",
"dust",
"airdrop",
"thin",
"unpriced",
"stale"
]
},
"chains": {
"type": "array",
"items": {
"type": "object",
"properties": {
"address": {
"type": "string"
},
"chainId": {
"type": "string"
},
"name": {
"type": "string"
},
"refreshedAt": {
"type": [
"string",
"null"
]
},
"refreshing": {
"type": "boolean"
},
"incomplete": {
"type": [
"string",
"null"
]
}
},
"required": [
"address",
"chainId",
"name",
"refreshedAt",
"refreshing",
"incomplete"
]
}
}
},
"required": [
"netWorthUsd",
"parts",
"byWallet",
"hidden",
"chains"
]
}

The MCP tool port_overview answers the same question ("what is my port worth, by wallet, and what is not counted") with the same figures, over the MCP server.

Every endpoint shares three: 401 for a missing or dead key, 402 for an account whose plan has no API ("Agents, MCP and the API are on Pro+ and above."), and 429 past the minute or day limit. The errors section has each body.