The Polygres SDK is a retrieval client for a per-project Runtime API. It uses a Polygres API key and Runtime API URL; it does not open direct Postgres connections or expose database passwords.
Links:
- Documentation: https://docs.evokoa.com/polygres
- Polygres: https://polygres.com
- Evokoa: https://evokoa.com
- X: https://x.com/evokoa_ai
- Discord: https://discord.gg/GnHR8ezuwG
- Product Hunt: https://www.producthunt.com/@evokoa
pip install polygresCreate a Polygres API key from your project Settings page. Find the Runtime API URL on your project Connect page. Use the Runtime API URL with the SDK, not the direct or pooled Postgres connection string.
from polygres import Polygres
client = Polygres(
api_key="POLYGRES_API_KEY",
runtime_url="POLYGRES_RUNTIME_URL",
)
project = client.project()
readiness = project.readiness()
print(readiness.graph, readiness.vector, readiness.hybrid)
connection = project.connection_info()
print(connection.direct_url_without_password)
print(connection.pooled_url_without_password)connection_info() returns passwordless direct and pooled connection strings.
The SDK never returns the database password.
Graph and hybrid calls need real row IDs from graph-registered tables. Do not
guess IDs such as doc_1 or cus_123 unless those rows actually exist in your
database. A safe pattern is to start with vector or text search, then use the
returned result as the graph start node.
embedding = [0.1] * 8 # Must match the configured vector dimensions.
vector_page = project.vector.search(
embedding,
config="documents_embedding",
limit=5,
)
top_doc = vector_page.results[0]
start = {
"schema": top_doc.schema,
"table": top_doc.table,
"id": top_doc.id,
}
graph_page = project.graph.expand(
start,
max_depth=2,
limit=10,
)
similar_page = project.vector.similar_to(
top_doc.id,
config="documents_embedding",
limit=5,
)
hybrid_page = project.hybrid.graph_first(
start,
embedding=embedding,
config="documents_embedding",
limit=10,
)
for result in hybrid_page.results:
print(result.id, result.score, result.vector_score, result.graph_score)If a graph call returns Node not found, check that:
schema,table, andidrefer to a real row.- The table is registered in graph configuration.
- The graph has been rebuilt after adding or changing that row.
readiness = project.readiness()
if readiness.vector["ready"]:
print("default vector config:", readiness.vector["default_config"])
connection = project.connection_info()
print(connection.direct_host)
print(connection.pooled_host)page = project.vector.search(
[0.1] * 8,
config="documents_embedding",
filters={"status": "published"},
min_similarity=0.75,
limit=10,
)
for result in page.results:
print(result.id, result.schema, result.table, result.score)Find rows similar to an existing row:
page = project.vector.similar_to(
row_id="doc_security_01178",
config="documents_embedding",
limit=10,
)Set include_values=True when you need returned embedding values:
page = project.vector.search(
[0.1] * 8,
config="documents_embedding",
include_values=True,
)TSVector full-text search:
page = project.text.tsvector(
"refund policy",
config="documents_body_tsv",
filters={"status": "published"},
limit=10,
)Fuzzy search:
page = project.text.fuzzy(
"acme corporation",
config="customer_name_fuzzy",
limit=10,
)Text results expose id, schema, table, properties, score, and
similarity.
Graph start nodes must identify real rows:
start = {"schema": "public", "table": "documents", "id": "doc_security_01178"}Expand from a node:
page = project.graph.expand(
start,
max_depth=2,
direction="any",
filters={"status": "published"},
limit=20,
)
for result in page.results:
print(result.node.id, result.depth, result.graph_score)Neighborhood is an alias-shaped traversal with radius:
page = project.graph.neighborhood(
start,
radius=2,
direction="any",
limit=20,
)Related returns one-hop related nodes:
page = project.graph.related(
start,
direction="any",
limit=20,
)Find paths between two nodes:
target = {"schema": "public", "table": "documents", "id": "doc_security_01744"}
path_response = project.graph.path(
start,
target,
max_depth=3,
)
print(path_response.paths)Find connections across a chain of entities:
connection_response = project.graph.connection(
[start, target],
max_depth=3,
)
print(connection_response.connections)GraphResult uses result.node.id. HybridResult exposes result.id
directly.
Graph-first starts from a graph node, then blends graph context with vector similarity:
page = project.hybrid.graph_first(
start,
embedding=[0.1] * 8,
config="documents_embedding",
max_depth=2,
limit=10,
)Vector-first starts with vector candidates, then expands graph context:
page = project.hybrid.vector_first(
[0.1] * 8,
config="documents_embedding",
vector_limit=20,
max_depth=1,
limit=10,
)Joint combines a vector query with a graph start node:
page = project.hybrid.joint(
[0.1] * 8,
start,
config="documents_embedding",
vector_weight=0.7,
graph_weight=0.3,
max_depth=2,
limit=10,
)Hybrid results expose id, schema, table, score, vector_score,
graph_score, distance, similarity, properties, and relationships.
Every list-style retrieval method returns a Page.
page = project.vector.search([0.1] * 8, config="documents_embedding", limit=25)
for result in page.results:
print(result.id)
if page.has_more:
next_page = project.vector.search(
[0.1] * 8,
config="documents_embedding",
limit=25,
cursor=page.next_cursor,
)Use auto_paging_iter() to iterate through all pages:
page = project.text.tsvector(
"security incident",
config="documents_body_tsv",
limit=25,
)
for result in page.auto_paging_iter():
print(result.id, result.score)from polygres import PolygresAPIError
try:
page = project.graph.expand(start, max_depth=2)
except PolygresAPIError as exc:
print(exc.status_code)
print(exc.code)
print(exc.request_id)
print(exc.details)Common graph failures include Node not found when the requested start or
target row is not present in the graph projection.
The SDK sends Authorization and User-Agent on every request. It does not
send X-Polygres-Project; the project identity is bound to the Runtime API URL.
The SDK supports retrieval against saved graph, vector, TSVector full-text, fuzzy text-search, and hybrid configurations. It does not expose dashboard-only setup mutations for graph/vector/text configuration, graph builds, or index reindexing.
The SDK is an HTTP client. It does not bundle direct Postgres drivers such as
asyncpg or psycopg, and it does not implement SQL editor script execution
locally. Future SQL editor SDK methods must call Polygres API routes instead of
opening database connections.