pointkit geocodes a plain address and hands back a POINT(longitude latitude) WKT string — the portable geometry format that Postgres, SQL Server, Oracle Spatial, SpatiaLite, and most GIS software all read directly.
Every serious spatial system reads WKT, which is exactly why it's worth having on hand even if you already use Postgres or MySQL day to day: it's what you paste into a one-off SQL Server or Oracle Spatial query, what QGIS and ArcGIS import without complaint, and what plenty of internal tools accept as a lowest-common-denominator geometry input.
The catch is the same one every spatial format shares: axis order. WKT is (longitude, latitude). Get a coordinate pair from somewhere that returns lat/long first — a lot of consumer mapping APIs do — and swap them by mistake, and the point silently lands somewhere else on Earth. pointkit geocodes the address directly, so the order is right from the start.
POINT(longitude latitude). It's read and written by Postgres/PostGIS, SQL Server, Oracle Spatial, SpatiaLite, and most GIS desktop software.ST_GeomFromText('POINT(...)', 4326). pointkit's Postgres output already does this wrapping for you; the WKT here is the bare geometry for anywhere else you need it.POINT(longitude latitude). Every major spatial format follows this except MySQL/MariaDB's default SRID 4326, which reverses it.